Repository navigation
Bootstrap verified pip trust before CI network installs - #359
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.
Verify pip trust before CI network installs
Refs durable-workflow/.github#237.
Use the reviewed, immutable organization bootstrap action immediately after Python setup and before the first dependency install in each affected job. It installs the fixed pip wheel from its explicit official URL with a required SHA-256, disables dependency resolution and version checks for that bootstrap, then inspects the effective bundled trust before later package requests. Existing package versions, protocol fixtures, runtime source, permissions and job budgets remain unchanged.
Local validation passes against the current central action/workflow policy. Normal repository checks remain required. This closes the affected CI bootstrap path only; it does not claim that a pip upgrade repairs an independently affected OS or application CA store, or qualify an existing published artifact. Image, release-builder and installed-consumer acceptance stay in their owning changes under the shared security issue.