Skip to content

Update aiohttp to 3.14.4 and yarl to 1.25.1 in platform locks - #530

Open
katsugtgz wants to merge 1 commit into
CraftOS-dev:mainfrom
katsugtgz:deps/aiohttp-3.14.4-yarl-1.25.1
Open

katsugtgz wants to merge 1 commit into
CraftOS-dev:mainfrom
katsugtgz:deps/aiohttp-3.14.4-yarl-1.25.1

Conversation

@katsugtgz

Copy link
Copy Markdown

Updates aiohttp to 3.14.4 and yarl to 1.25.1 in the three platform locks.

Evidence:

  • requirements/lock-linux_x86_64-py310.txt, requirements/lock-macosx_arm64-py310.txt, and requirements/lock-win_amd64-py310.txt pinned aiohttp==3.14.3
  • osv-scanner reported 24 aiohttp advisories on the pinned version, including GHSA-28qf-cpwq-vmc2, GHSA-24c4-3p7v-29cm, GHSA-3rp8-rxj8-mvjw, and GHSA-h4cc-hm5h-fmm9
  • aiohttp 3.14.4 requires yarl>=1.25.1, so the locks also move yarl from 1.24.5 to 1.25.1 (its own requirements are unchanged and satisfied by the existing pins)

Validation:

  • osv-scanner no longer reports any aiohttp or yarl advisory on the updated locks; 19 other packages in the lock still report separate advisories and are untouched here
  • sha256 of the six new wheel hashes (aiohttp and yarl, cp310, linux/win/macos) verified against PyPI by download
  • python scripts/generate_lock.py --check passes on all three locks
  • dependency metadata of aiohttp 3.14.4 and yarl 1.25.1 checked against every pin in the linux lock: all satisfied

Scope: dependency lock update only, requirements/lock-*.txt entries. requirements.txt stays unpinned per the lock design, so the header source digest is unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant