fix: force aiohttp>=3.14.0 for GHSA-jg22-mg44-37j8, GHSA-hg6j-4rv6-33pg#6041
fix: force aiohttp>=3.14.0 for GHSA-jg22-mg44-37j8, GHSA-hg6j-4rv6-33pg#6041greysonlalonde wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the Changesaiohttp Security Version Floor Enforcement
🎯 2 (Simple) | ⏱️ ~5 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
What
Force
aiohttp>=3.14.0via[tool.uv] override-dependenciesto remediate two advisories flagged bypip-audit:aiohttp is a transitive dependency; the lock previously resolved it to 3.13.4.
Why a per-package exclude-newer
The repo enforces
exclude-newer = "3 days". aiohttp 3.14.0 was published 2026-06-01, inside that window, so a normaluv lockcould not select it. Added a tightexclude-newer-package = { aiohttp = "2026-06-02T00:00:00Z" }so only 3.14.0 (and nothing newer) becomes eligible, consistent with the existing security-override convention in[tool.uv].Other pip-audit findings (not in this PR)
uv sync.Verification
uv lockupdates only aiohttp 3.13.4 -> 3.14.0; no other package versions change.uv-lockconsistency check passes.Note
Low Risk
Dependency-only security bump with no application code changes; minor risk from aiohttp minor-version upgrade in transitive HTTP stacks.
Overview
Remediates two pip-audit advisories on transitive aiohttp by pinning
aiohttp>=3.14.0in[tool.uv] override-dependenciesand refreshinguv.lock(3.13.4 → 3.14.0).Because the repo’s
exclude-newer = "3 days"would block 3.14.0 (released 2026-06-01), the PR adds a narrowexclude-newer-packageentry for aiohttp so the override can resolve without widening the global freshness policy.Reviewed by Cursor Bugbot for commit 591db52. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
aiohttpcompatibility and enforce security requirements. Improved dependency resolution configuration for better stability.