Skip to content

Upgrade locked packages that have published security advisories - #102

Merged
haruotsu merged 1 commit into
mainfrom
upgrade-vulnerable-deps
Nov 10, 2026
Merged

haruotsu merged 1 commit into
mainfrom
upgrade-vulnerable-deps

Conversation

@haruotsu

Copy link
Copy Markdown
Collaborator

The lock pinned several packages with published security advisories, some of them critical. This moves each of them to its latest release rather than the first patched one, so the next advisory against an older line does not bring the same work back.

Package Before After
authlib 1.7.2 1.9.5
certifi 2026.7.22 2026.10.23
pyasn1 0.6.4 0.6.5
joserfc 1.7.4 1.8.0
mcp 1.29.0 1.30.0
aiohttp 3.14.3 3.14.5
multidict 6.7.1 7.2.1
pyjwt 2.13.0 2.15.1
urllib3 2.7.0 2.8.0
yarl 1.24.5 1.25.1 (follows aiohttp)

Only uv.lock changes. gete imports none of these directly. multidict crosses a major version, but it reaches gete only through aiohttp and yarl, which accept it.

Not included

  • opentelemetry-api stays at 1.42.1. google-adk 2.9 caps it at <=1.42.1, so moving past it means widening the ADK range, which needs its own verification.
  • One pyjwt advisory has no patched release yet.

Scope

Deployed agents do not use this lock. Their requirements.txt is built from version ranges and resolved when Agent Engine builds the image. So this covers gete's own development and CI environment.

Checks

uv lock --check, ruff check, ruff format --check, mypy, and pytest (1026 passed) all pass locally.

The lock held versions of authlib, certifi, pyasn1, joserfc, mcp, aiohttp,
multidict, pyjwt, and urllib3 with known advisories, some of them critical.
Each is moved to its latest release rather than the first patched one, so
the next advisory against an older line does not reopen the same work.
yarl follows aiohttp.

opentelemetry-api stays at 1.42.1: google-adk 2.9 caps it there, and moving
past it means widening the ADK range, which needs its own verification.

🤖 Generated with Claude Code
@haruotsu
haruotsu merged commit aded411 into main Nov 10, 2026
3 checks passed
@haruotsu
haruotsu deleted the upgrade-vulnerable-deps branch November 10, 2026 04:45
@github-actions github-actions Bot mentioned this pull request Nov 10, 2026
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