Repository navigation
chore: restore merge gate after verified 0.1.1 cutover - #53
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.
Restore the normal deployment-level merge authorization after the v0.1.1 immutable-source cutover. This changes only MERGE_DEPLOYMENT_AUTHORIZED and its exact backend test expectation, preserving the pinned reviewed runner bf0510e, CLI-only flags, credentials, quotas and repository opt-in policies.
The production gate remains closed until the operator independently verifies the closed-gate Worker deployment, both actual caller pins, OIDC credential-only diagnostics, active deployment bindings and health. Merging this PR does not deploy or open production; deployment of this revision is explicitly conditioned on those acceptance checks. No inference, feature-PR merge or repository-policy change is triggered.
PR50 contains the live-tested runtime correction; PR51 versions that source; PR52 and caller PRs KMU185/TopkAPI30 coordinate the exact versioned source SHA. Full CI validates this two-line maintenance change. This restores the original authorized deployment setting; automatic merging still requires the repository's separate policy and all GitHub protections.