chore(deps): bump anyio from 4.12.1 to 4.14.2 - #1892
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [anyio](https://github.com/agronholm/anyio) from 4.12.1 to 4.14.2. - [Release notes](https://github.com/agronholm/anyio/releases) - [Commits](agronholm/anyio@4.12.1...4.14.2) --- updated-dependencies: - dependency-name: anyio dependency-version: 4.14.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Looks good, routine dependency bump. Checked the lockfile diff: anyio 4.12.1 to 4.14.2 (upstream bugfix release, no breaking changes noted), exceptiongroup's typing-extensions marker widened to unconditional (uv resolver metadata), and the standard exclude-newer reset — no application code changes.
Extended reasoning...
Overview
The only changed file is uv.lock, a Dependabot-generated lockfile update. Three changes: (1) the exclude-newer field reset to the epoch placeholder with an added comment, which is a standard uv artifact unrelated to actual dependency resolution; (2) anyio bumped from 4.12.1 to 4.14.2 with updated sdist/wheel URLs and hashes; (3) exceptiongroup's dependency on typing-extensions had its Python-version marker removed, making it unconditional — likely because newer resolver metadata for exceptiongroup 1.3.1 reports this dependency unconditionally rather than an actual behavioral change caused by this PR.
Security risks
No security risk. This is a lockfile metadata change with no application source code touched. anyio and exceptiongroup are both well-maintained, widely used libraries; the version bump is a minor/patch upgrade per semver, and the release notes describe bugfixes (CPU spin fix, capacity limiter fixes) rather than any security patches that would need extra scrutiny, though even if there were, that would argue for updating rather than blocking.
Level of scrutiny
Low. This is exactly the kind of mechanical, low-ambiguity change (version bump, generated lockfile) that fits the approval criteria: no design decisions, no critical/security-sensitive code paths touched, and it's an automated dependency update following established patterns (Dependabot PR).
Other factors
No CLAUDE.md conventions apply. No CODEOWNERS concerns identified for uv.lock. No prior review history or outstanding objections exist on this PR (fresh dependabot PR, no prior comments). The bug hunting system found no issues, consistent with the trivial nature of the change.
Bumps anyio from 4.12.1 to 4.14.2.
Release notes
Sourced from anyio's releases.
... (truncated)
Commits
c384f99Bumped up the versiondbba29dFixed 100% CPU spin on cancel scope misuse (#1217)6bbc6c3Fix CapacityLimiter over-granting tokens on asyncio (#1172)6f82b25Refactored TestTLSStream.test_receive_invalid_max_bytes() to be less flakybe24b04Relaxed timeouts to fix test flakiness8113506Fix test flakiness caused by slow callback duration logging1e988b6Fixed CapacityLimiter raising trio.WouldBlock instead of anyio.WouldBlock (#1...44713f3Pin setup-uv to a commit sha across downstream jobs (#1213)f1b7301Fixed stderr writes in a worker subprocess causing a deadlock (#1207)212be93Fix flaky test_tcp_listener_same_port using a hardcoded port (#1206)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.