Repository navigation
chore: align CodexBot immutable review source - #46
Merged
Merged
Conversation
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
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.
Pin the Worker and backend expectation to the actual reviewed PR #44 merge
14804ea42e9fd9f4e78d4501356e0ed73355bfbe. Coordinate the same exact immutable revision with KMU #183 and TopkAPI #20. Both caller PRs change only their existing workflow SHA.PR #45 established the documented maintenance state; the deployed merge gate is closed and live D1 checks confirmed no outstanding merge intents or reviews. This PR also restores the reviewed target gate value to true. For cutover, deploy this code with the explicit
--var MERGE_DEPLOYMENT_AUTHORIZED:falsemaintenance override, verify the actual Worker version and caller SHAs, run non-inference acceptance, then deploy without the override to reopen the gate. Never deploy the target true setting before those checks.No credentials, quotas, repository review/merge policies, secrets, schema, business code or unrelated PRs are changed. No inference or feature-PR merge is part of this rollout. Normal required CI and qualified approvals remain enforced.