Repository navigation
fix: deploy shared candidate Contents and Check Runs readers - #48
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.
Deploy protected build #284 (2b2903e463d28891b5688bf4546da99a299c3684) to the two existing native candidate/postmerge reader workflows. The shared repair accepts GitHub's legitimate line-wrapped base64 and verifies the decoded Git blob digest; it continues to reject corrupt/duplicate-key/mismatched/oversized source bytes. Grant checks/read only to those two already-read-only caller jobs, matching the shared jobs' actual Check Runs GETs.
The operator/schedule pin cad131c1..., original detector/candidate workflow pins, attested Signer pin 5756b3c5..., signed-audit pin, source manifest, candidate/release policies and every existing required check remain unchanged. No App/Secret, WRITE privilege, protection exception or formal Release activation.
Central original PR and genuine protected-main/push CI succeeded, including a real immutable Contents GET/hash check. Both manual and projected future-policy Python suites passed (68 each). Require native exact-head App15368 Windows PG14–18/resolver/summary and all additional repository-required checks before expected-head protected squash. Verify new main/push separately; ordinary pin-update CI is not a genuine signed stable-candidate E2E.
Tracking: pgextwin/build#75