Repository navigation
Chore(deps): Bump aiohttp from 3.14.3 to 3.14.4 - #1277
Conversation
foxpatch-aleph
left a comment
There was a problem hiding this comment.
Low-risk one-line patch bump of aiohttp from 3.14.3 to 3.14.4 in pyproject.toml. The version is the only aiohttp pin in the repo (no lock files or Docker pins exist), 3.14.4 provides wheels for the project's supported Pythons (3.12/3.13) and declares Requires-Python >=3.10, and none of its transitive dependencies (yarl, multidict, frozenlist, propcache, aiohappyeyeballs) are pinned elsewhere in the project, so no resolution conflicts. No code changes, so existing CI tests are sufficient validation.
pyproject.toml (line 27): Non-blocking: aiohttp 3.14.5 is already published on PyPI, so this bump will be one patch release behind on merge. Fine to merge as-is since patch releases within 3.14.x carry no API changes; Dependabot can follow up with the 3.14.5 bump.
foxpatch-aleph
left a comment
There was a problem hiding this comment.
Routine dependabot patch bump of aiohttp from 3.14.3 to 3.14.4, applied in the single canonical dependency list in pyproject.toml. No other pins of aiohttp exist in the repo, aiohttp 3.14.4 resolves and imports cleanly on Python 3.12 alongside the pinned aiohttp-cors 0.8.1, and the codebase relies only on public aiohttp APIs, so the patch-level change is low risk. The local hatch test env could not be built in this sandbox due to a pre-existing py-ed25519-bindings build issue unrelated to this change; CI will exercise the suite. One stale adjacent comment about the uvloop pin referencing aiohttp v3.13.3 is noted but out of scope.
pyproject.toml (line 72): Non-blocking, out of scope for this bump: the comment justifying the uvloop>=0.21,<0.22 pin still reads "Pinned to 0.21 as long as we use aiohttp v3.13.3". The project is now on aiohttp 3.14.x, so this rationale is stale — consider a follow-up to re-test uvloop 0.22 compatibility and either relax the pin or update the comment.
Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.14.3 to 3.14.4. --- updated-dependencies: - dependency-name: aiohttp dependency-version: 3.14.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
01f5b08 to
20e4873
Compare
foxpatch-aleph
left a comment
There was a problem hiding this comment.
Minimal, correct one-line pin bump of aiohttp 3.14.3 to 3.14.4, matching the project's pinned-dependency convention. The 3.14.4 release is a bug-fix and hardening update containing several security-relevant fixes beneficial to a public-facing node (WebSocket reader DoS fixes, Set-Cookie parsing hardening, absolute-form request-target scheme trust fix, Secure-cookie leak fixes). The only behavioral change with rejection semantics, the new client_max_fields=1000 cap on urlencoded form parsing in BaseRequest.post(), does not affect pyaleph because no code path calls request.post() and the upload endpoints use request.multipart() directly. The StreamResponse slots fix is also safe since pyaleph only instantiates StreamResponse without subclassing it or assigning ad-hoc attributes. CI resolves dependencies from pyproject.toml via hatch, so the test suite will exercise the new version.
pyproject.toml (line 74): Non-blocking, pre-existing: this comment still says "Pinned to 0.21 as long as we use aiohttp v3.13.3", but with this PR the project is on aiohttp 3.14.4. The comment (and possibly the pin itself) is stale and could be revisited in a follow-up if uvloop compatibility has since been resolved.
Bumps aiohttp from 3.14.3 to 3.14.4.