Repository navigation
chore: close merge gate for PR47 coordinated rollout - #48
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.
Close the deployment merge gate for the authorized PR #47 rollout. This changes only MERGE_DEPLOYMENT_AUTHORIZED and its backend-test expectation; the existing trusted workflow SHA remains unchanged.
Source PR #47 is already merged at 560083b, and its merge-commit CI passed. Follow docs/operations.md: merge this maintenance PR normally, deploy the closed gate, drain/reconcile merge intents, then use scripts/prepare-pin-upgrade.mjs for the exact source SHA and both API-only caller updates. Restore the gate only after coordinated deployment, caller trust and credential-only OIDC checks pass.
Validation: npm run check (242 tests, typecheck, lint, build) and Wrangler deployment dry-run passed. This PR does not deploy, change credentials, reset data/quotas, alter review policies or trigger inference. No caller application files are changed.