Repository navigation
fix(deps): patch aiohttp advisories independently of Japanese resources - #243
Merged
Merged
Conversation
This was referenced Oct 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.
What and why
The required dependency audit now rejects main's aiohttp 3.14.3 pin following
the published advisories. Update aiohttp to 3.14.4 and its minimum required yarl
to 1.25.1. These are the only two changed package versions in the lock.
This extracts the dependency-only patch from draft #237 so security maintenance
does not depend on the Japanese pronunciation resource review.
Upstream: advisory,
3.14.4 release.
Change class
Owning layer: dependency pins and generated lock.
User-visible effect: patched HTTP dependencies; no feature/configuration change.
Compatibility: yarl's required minimum follows aiohttp. Speech/GPU pins and
optional profile selections are unchanged.
Evidence
lifecycle tests passed.
uv lock --check --offlinepasses; inspected lock changes show only aiohttp3.14.3 → 3.14.4 and yarl 1.24.5 → 1.25.1.
exception unchanged; no new vulnerability suppression.
This PR's fresh CI is tracked independently.
Final check