Repository navigation
fix(issue75): pin central fresh-fleet scheduled replay - #24
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.
One-line immutable common workflow SHA: central protected build/main
bd35b7c702f80568b3bdd2cea235bac9930d095f(PR #240 merged, original PR and main/push required CI successful). Scheduled candidate authorization preserves actual completed central scan, source Git blob identity, fresh 17-fleet replay, protected local main and double GET drift denial. No formal Release, Publisher scope or policy change; keep PUBLISH_DENY and GO B/G4/G5 NO_GO. No interaction with pg_bigm #46 or orafce safety-held write.