Skip to content

codex: add exact release pin recovery #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ttaylorr-oai merged 1 commit into from
Aug 7, 2026
+792 −8
Merged

codex: add exact release pin recovery #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions .github/CODEX.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,23 @@ earlier bootstrap commit cannot lose one of its retained objects while the
next direct transition is prepared. After the first v3 publication, ordinary
topic approval or explicit plan review is required.

The checked-in `codex.release-recovery` file is a one-shot rollout
exception for the release-metadata commit that landed after the v2 snapshot
but before this first v3 publication. After landing its controller support,
run:

```sh
Meta/codex recover-release-pin --remote origin \
--expected-meta <exact-post-controller-meta-sha> \
--authorization '<explicit authorization>'
```

The command accepts only the exact reviewed manifest: unchanged v3 plan
blobs from the recorded baseline, the `ba107` to `40589` release step, merged
PR #22, an absent new pin, and an unchanged release row shape. It atomically
creates that one pin, changes only `codex.plan`, and deletes the manifest.
Once used, it cannot authorize another transition.

## Repository settings

Apply the checked-in ruleset recipes after the v3 publication:
Expand Down
Loading