Repository navigation
fix: bind genuine scheduled fleet verifier to protected source - #50
Merged
ShutenOishi merged 1 commit intoOct 25, 2026
Merged
Conversation
ShutenOishi
enabled auto-merge (squash)
October 25, 2026 14:25
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.
pgextwin/build#75. One-line immutable shared operator pin cad131c1 → 90755b09. Independent protected Git tree audit proved 2/6 scanner/policy source blobs on old pin differ from the current central source, causing genuine local schedules to DENY. Pinning the already-protected central source fixes immutable replay-source consistency without weakening source equality. A fresh central and local event=schedule, current protected main identities, 3h TTL, exact registered fleet, App15368 PG14–18/resolver/summary, native bot PR identity, immutable upstream SHA, signatures and Publisher independent gates remain mandatory. No release/policy change; PUBLISH_DENY and GO B/G4/G5 NO_GO preserved. Require original exact-head CI and protected auto-merge/postmerge.