Repository navigation
Lock virtualenv 21.14.1 for four advisories - #26
Merged
Merged
Conversation
Every virtualenv release below 21.7.13 is affected by PYSEC-2026-4011, -4012, -4013 and -4014. virtualenv arrives through pre-commit in the dev dependencies. The lock moves only virtualenv and its own dependencies: - virtualenv: 21.7.9 -> 21.14.1
mahdi-shafiei
force-pushed
the
fix/virtualenv-21.14
branch
from
September 30, 2026 18:10
900dcbe to
cde66ca
Compare
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
1 participant
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.
Locks virtualenv 21.14.1, which closes four advisories published 2026-09-30 against every virtualenv release below 21.7.13:
virtualenv enters through pre-commit in the dev dependencies. Only
uv.lockchanges, produced byuv lock --upgrade-package virtualenv(uv 0.12.21).Package changes
No other package moves; the
resolution-markersset is unchanged.Audit
The audit reproduces the Security workflow's install set from the lock, with a fresh advisory cache:
No other advisory is reported on the new lock.
Note on the Security workflow: its step
uv run --with pip-audit pip-audit --localreported "No known vulnerabilities found" on this branch before the rebase, while the synced environment held urllib3 2.7.0 (three advisories at the time). The--withoverlay installs pip-audit's own 29 packages, and--localappears to restrict the audit to that overlay, so the job does not see the project dependencies. That is outside this change and left for a separate fix.