Repository navigation
deps: move versions.lock past new advisories (certifi, filelock, virtualenv) - #13
Merged
Merged
Conversation
…ualenv) CI's pip-audit started failing every PR on advisories published this week against three pins: - certifi 2026.5.20 -> 2026.10.19 (PYSEC-2026-4320). This one ships: the container image installs from versions.lock. - filelock 3.29.0 -> 4.2.1 (three CVEs; no 3.x fix exists). Used only by virtualenv and python-discovery, both pre-commit tooling. Both accept 4.x (virtualenv: >=3.24.2,<5; python-discovery: >=3.16.1), and 4.2.1 needs Python 3.11, SENTINEL's floor. - virtualenv 21.7.13 -> 21.14.10 (eleven CVEs; 21.14.9 still had one more, CVE-2026-113713, fixed in 21.14.10). Its requirements raise packaging to 26.3 and distlib to 0.4.3, the smallest versions that satisfy them. Smallest fixed versions throughout, as CONTRIBUTING asks. pip-audit 2.10.1, run exactly as CI runs it, now finds no known vulnerabilities; scripts/check_versions_lock.py reports 0 conflicts; pip check finds no broken requirements; the full suite passes on the new pins. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What and why
CI's
pip-auditstarted failing every PR (#11 and #12 included) on advisories published this week againstversions.lock. Merge this first; the other open PRs' audit job passes once it is onmain.>=26.3)>=0.4.3)Smallest fixed or required versions, per CONTRIBUTING. filelock 4.2.1 needs Python 3.11, SENTINEL's floor. Requirements were checked on PyPI before bumping.
Testing
pip-audit==2.10.1, run exactly as CI runs it (-r versions.lock --no-deps --disable-pip, same ignore): no known vulnerabilities.scripts/check_versions_lock.py: 0 conflicts.pip check: no broken requirements.ruffandmypy --strictclean. The pre-commit hooks (gitleaks) ran on the commit with the new virtualenv.Security invariants
🤖 Generated with Claude Code