Repository navigation
build: bump anyio to 4.15.1 in uv.lock to clear two CVEs - #17
Merged
Merged
Conversation
`uv lock --upgrade-package anyio` resolves anyio 4.11.0 -> 4.15.1, past the 4.14.2 floor that fixes CVE-2026-63374 (TLS certificate spoofing via IDNA host encoding) and CVE-2026-64847 (process-pool worker stall on undrained stderr). anyio >=4.13 vendors sniffio, so sniffio drops from the lockfile; typing-extensions gains a marker-split 4.16.0 entry alongside 4.15.0. pyproject.toml is unchanged; consumers still resolve their own anyio from httpx>=0.27.0. This clears the two Dependabot alerts and the `audit` CI job, which pip-audit fails on the current lock and passes on the new one. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: man8/targetprocess-py/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
man8
approved these changes
Sep 20, 2026
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
Bumps
anyioinuv.lockto clear two open security advisories (both transitive, viahttpx→httpcore→anyio) and turn the repository'sauditCI job green.Changes
uv lock --upgrade-package anyio: anyio4.11.0→4.15.1(past the4.14.2fix floor for both advisories below).sniffiois removed from the lockfile — anyio>=4.13vendors it and nothing else in the dependency graph requires it standalone.typing-extensionsgains a marker-split entry (4.16.0alongside the existing4.15.0), a resolver-cascade side effect of anyio's own tightened constraint, applied consistently everywheretyping-extensionsappears (anyio, mypy, pydantic, pydantic-core, pytest-asyncio, typing-inspection).pyproject.tomlis untouched — byte-identical to its state before this change. Consumers of this library resolve their ownanyiovia the existinghttpx>=0.27.0constraint, so no floor is added here; that's a separate decision this PR deliberately does not make.Testing
auditjob's own commands, before and after, in the worktree:uvx pip-audit --strict --no-deps --disable-pip --progress-spinner off→ 2 known vulnerabilities, exit 1 (anyio 4.11.0 CVE-2026-63374,anyio 4.11.0 CVE-2026-64847).uv run pytest -q→ 1450 passed, no failures, includingtests/test_transport.py(6 passed), which exercises the async httpx transport path directly — anyio is httpx's async backend, and this bump crosses anyio 4.13's removal of its ownsniffiodependency.Context
Two Dependabot security-update runs for this advisory pair both failed with
security_update_not_possible, despite each reportinglatest-resolvable-version: 4.14.2andconflicting-dependencies: []in their own payload — i.e. Dependabot's own numbers say the fix resolves cleanly, but it declined to open a PR. This PR is that same resolve, run and verified locally. The Dependabot automation defect itself is out of scope here.Checklist
uv run ruff check .anduv run ruff format --check .passuv run mypy --strict srcpassesuv run pytest -qpasses and coverage stays at or above 90%uv run pre-commit run --all-files --hook-stage pre-commitpassesuv run pre-commit run --all-files --hook-stage pre-pushpassesTODO/FIXME/HACK/XXXmarkers name an issue — none added🤖 Generated with Claude Code