Skip to content

fix: restore strict scheduled fleet source closure - #41

Merged
ShutenOishi merged 1 commit into
mainfrom
fix/schedule-source-closure-20261027
Oct 27, 2026
Merged

ShutenOishi merged 1 commit into
mainfrom
fix/schedule-source-closure-20261027

Conversation

@ShutenOishi

Copy link
Copy Markdown
Contributor

Authentic pgtap schedule Run 40418179041 proves a fleet-wide immutable source-closure mismatch: old central 9ec4dde... scanner workflow blob 39b5aed... differs from current protected central 45620f4... blob 1eb3a68.... All six scan replay blobs match protected dbf7365... / bc91ca8... / current 45620f4....

Update ONLY the three schedule-only reusable caller pins in .github/workflows/update-watch.yml to verified protected dbf7365.... Keep historical detector, signed/independent audit pins, candidate-only conditions, permissions, and PUBLISH_DENY unchanged. Require new native App15368 PG14–18/summary CI before expected-head protected merge, followed by genuine main/push and later real schedule regression. No synthetic schedule or Release. Tracks pgextwin/build#75.

@ShutenOishi
ShutenOishi marked this pull request as ready for review October 27, 2026 00:46
@ShutenOishi
ShutenOishi merged commit e430b3a into main Oct 27, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant