Repository navigation
Conversation
setup-uv's `python-version: '3.13'` exports UV_PYTHON=3.13 for the rest of the caller's job. It overrode their .python-version and requires-python: `uv export` failed for projects with requires-python < 3.13, and their later `uv run`/`uv sync` steps got Python 3.13. The audit step now passes `--python 3.13` to its own `uv run` instead. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Clean fixtures pinned exact versions, so every new advisory against a pin turned "Validate results" red with no code change. Cases 01, 02 and 11 now use `>=`, and cases 06 and 09 no longer commit uv.lock and Pipfile.lock: CI generates them before the action, as for 04, 07 and 10. The deliberately vulnerable cases (03, 05, 08) stay pinned, and the validation checks are unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
✅ All test workflows behaved as expected13 passed, 0 failed
|
This branch has not been deployed
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.
The action's setup-uv step set
python-version: '3.13', which exportsUV_PYTHON=3.13for the rest of the caller's job:uv exportfailed for projects withrequires-python < 3.13, and the caller's lateruvsteps ran on Python 3.13. The audit step now passes--python 3.13to its ownuv runinstead. The clean integration fixtures also stop pinning versions and committing lockfiles, so a new advisory no longer turns "Validate results" red with no code change; the deliberately vulnerable fixtures stay pinned.For reviewers: later steps in the caller's job no longer get
UV_PYTHON=3.13, and whenuv exportre-resolves (nouv.lock, or a stale one) it now uses the project's own Python. That may download one on hosted runners, and offline with downloads disabled it fails if no matching interpreter exists, the same constraint as forcing 3.13 before.Author attestation
AI-assisted: Claude Code wrote the changes and ran the local checks: pytest, mypy, pre-commit, end-to-end runs of the audit step against v1.0.0 and a replay of the integration matrix.