Repository navigation
Restore merge gate after verified 0.1.3 cutover - #62
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.
Summary
Restore the deployment merge gate after the authorized 0.1.3 immutable-pin cutover. Exactly two lines change: the gate and its backend test expectation.
Merging does not deploy. The operator will deploy this reviewed revision only after the closed-gate Worker trusts
23018028dc656100c1b313a01bf20e7109b8258a, both live caller pins match, and credential-only OIDC acceptance succeeds. Repository authorization, explicit-only merge policies, human-approval settings, credentials and browser/hosted-inference flags remain unchanged.Evidence
1d83827c-8053-402e-bb62-f01f23d3bf01has its merge gate closed; no active reviews or merge intents were present.After: the gate can be restored from a reviewed commit after cutover validation. Six focused backend/workflow checks passed; full CI runs on this PR.
Merge Danger
Door: two-way
Blast Radius: deployment
Deploy only after verified trust/OIDC cutover. This flag permits existing opted-in merge policies; it does not authorize an unrequested merge or bypass GitHub rules.