Repository navigation
fix(setup): install setuptools>=83 in pip venvs - #42
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.
Problem
Consumer runs 37935721195, 37940750631, and 37119136109 fail their Python security check because the pip-toolchain venv retains the interpreter-bundled setuptools 79.0.1. The exact audit output is:
Change
The PR diff changes exactly two files:
scripts/setup.sh: +1 line, upgradingsetuptools>=83.0.0in the pip + venv branch.scripts/setup.ps1: +2 lines, adding the equivalent setuptools upgrade and failure check.Acceptance
Section D with ambient Python 3.12.3 exited
0. Literal output:Section D with
python3resolving through the PATH shim to Python 3.11.16 exited0. Literal output:CI on this PR
Template CI run 38048152406 on head
5134a8b53c7b16d85a483f2043d33a1b98a9ccb9completed with conclusionfailure.The
securityjob (Python 3.11) and dependentci-passedaggregate are red because the job runs the released.github/scripts/setup.sh, which this PR must not touch. The released copy is refreshed only by the post-v1.0.7 self-update PR. The security log contains exactly these two audit rows and no other vulnerability-ID rows:All other executed jobs succeeded; the conditional Org OpenSSF Scorecard job was skipped.
Release state
v1points tod12884de43b9f47b8f47721a6ea1977bdc2a4cbb(v1.0.6), the release drift check is green, andv1.0remains absent until v1.0.7.Merge path
The branch was updated from
mainby merge commit5134a8b53c7b16d85a483f2043d33a1b98a9ccb9before Section D and CI were rerun. Merging requires an explicit admin bypass of the requiredci-passedcheck; the owner decides after P4.Do not merge: P4 clean-room review pending