Codex plan: add tb/codex/release-tooling in codex - #84
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
ttaylorr-oai
deleted the
codex-plan/codex-release-tooling-4209f5e2907f
branch
September 7, 2026 20:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Admit the approved release workflow from #83 as a stable topic after
tb/codex/lto-pgo. The source boundary is the existing PGO pin, so replayuses the three-file change reviewed in #83. All existing stable and preview
topics retain their order, source pins, and prerequisites.
4209f5e2907f3e96266ce9eabe8db70653dbaef988fcb4ac12c583bedf010e97ebf83cec240e3120refs/heads/codex-pins/4209f5e2907f3e96266ce9eabe8db70653dbaef9The current trusted controller generated this eight-line addition and
validated the topic approval and plan policy. This admits the desired
source; the normal rebuild and staging checks still govern publication.