Repository navigation
chore: pin merged App approval fix - #37
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.
Coordinate the Worker trust and exact backend expectation to the actual merged approval fix from #36: 17608a5.
Only the two immutable SHA references change. The active caller setup branch was updated to the same revision without changing its manual-review policy, explicit-only merge policy, protected Environment guards or named secret grants. Deleted/disabled acceptance and TopkAPI callers are not reactivated.
The production merge gate was closed using an operator deployment override and verified from Worker version 461ec534-7261-4a55-8ed9-585113acda5d; D1 showed zero active review/merge intents. The existing pinUpgrade validator checked the observed maintenance configuration and caller secret isolation. The declared normal merge gate remains unchanged and is restored only by deploying the reviewed coordinated pin.
Validation: focused backend/pin regression tests passed; normal full CI remains required. No live inference, new credential provisioning, D1 migration or repository protection changes.