Repository navigation
security: approve fixed trust bootstrap and crates OIDC action - #238
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
2 participants
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.
Refs #237.
Approve two reviewed immutable action commits: our patched-pip bootstrap from #236 and the official rust-lang crates.io OIDC action v1.0.5. The latter masks its short-lived credential, binds the GitHub OIDC audience to the registry and revokes the credential in its post step. Both use supported action runtimes.
The existing preflight's exact five-step shape otherwise rejects adding the patched-pip bootstrap before the PyYAML installation. Permit only that exact pinned bootstrap at that position; retain the original five-step form during the rollout. All existing dependency-command, protected central checkout, read-only permissions and required-gate checks remain. Focused controls refuse a different pin, an
if: false, a shell replacement and a bootstrap moved after the dependency installation.All 19 existing policy tests pass with those added refusal controls. Both proposed SDK Rust and SDK Python workflow directories pass the complete policy validator using this source. No new release authority or broader action allowance is introduced.