Clear pip-audit: raise anyio and audit uv.lock - #57
Merged
Merged
Conversation
anyio 4.13.0 carries CVE-2026-63374 and CVE-2026-64847, failing the blocking audit step in QA. Upgrade the lock to the fixed release and add a constraint floor so a future re-resolution cannot drop back below it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
LGTM! Fire in the disco! |
pip-audit identifies installed packages by name and version only, so it matched our loguru-config fork (a git source) against the unrelated loguru-config project on PyPI. Exporting the lockfile hands the fork to pip-audit as a URL requirement, which it skips rather than misattributes, and drops the scrobbledb self-audit notice. The export covers every extra and group; pipefail keeps a failed export from passing as a clean audit. 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.
Summary
The blocking
pip-auditstep in QA has been failing onmainsince #56 (and onfeat/datasette-readonly-enforcement). Lint, type checks and tests all passed; the audit flagged anyio 4.13.0:Both are fixed in 4.14.2. anyio is transitive (via httpx, starlette and mcp, pulled in by pylast, datasette and datasette-mcp).
While in here, the audit itself was also fixed. It checked the installed environment, and pip-audit identifies installed packages by name and version only, so our
loguru-configfork (a git source) was being matched against the unrelatedloguru-configproject on PyPI (erezinman/loguru-config).Changes
uv.lock: anyio 4.13.0 → 4.14.2; no other packages moved.pyproject.toml[tool.uv]: addanyio>=4.14.2toconstraint-dependencies, alongside the existing pip and msgpack floors, so a re-resolution can't drop back below the fix.pyproject.tomlauditpoe task: audituv.lockinstead of the environment:--no-emit-projectdrops the "scrobbledb not on PyPI" skip notice.uv syncinstalls.pipefailmakes a failed export fail the task instead of auditing an empty list as clean.Trade-offs
Verification
uv run poe audit: no known vulnerabilities found;loguru-configis the only skip.uv.lock: the task exits 2.uv run poe test:quick: 883 passed, 2 skipped.feat/datasette-readonly-enforcementwill need a rebase ontomainonce this lands.🤖 Generated with Claude Code