fix: refresh lockfile with aiohttp 3.13.5#208
Merged
scale-ballen merged 3 commits intomainfrom Apr 29, 2026
Merged
Conversation
…mv-4862 Aqua/trivy flagged `egp-mirror-int/agentex:*-fips` for HIGH advisory GHSA-xqmj-j6mv-4862 ("Server-Side Template Injection in /prompts/test endpoint") — vulnerable range `>= 1.80.5, < 1.83.7`, patched in `>= 1.83.7`. Current pin `litellm>=1.48.2,<2` resolved to 1.83.0 in the latest image build, which is in the vulnerable range. This change: - Bumps `litellm` floor in `agentex/pyproject.toml` from `>=1.48.2,<2` to `>=1.83.7,<2`. The new floor automatically dodges the litellm 1.82.7/1.82.8 supply-chain compromise (PR #195 was protecting against that with `<1.82.7`; this PR supersedes that need by setting the floor above those versions). - Widens the test extra `httpx[http2]` upper bound to `<0.29` because litellm 1.83.7 transitively requires `httpx==0.28.1`. - Adds a workspace `override-dependencies` entry for `httpx[http2]>=0.28.1` to override the pinned `httpx<0.28` constraint in `agentex-sdk`. - Regenerates `uv.lock`. Reachability: agentex consumes litellm as an SDK (`litellm.acompletion`, `litellm.types.*`, etc.); the vulnerable code path lives in `litellm.proxy.*` and is not invoked at runtime here. Scanner flags by package version regardless, so the bump is required to clear Aqua. Closes / supersedes #195 (which was pinning `<1.82.7` for the 1.82.7/1.82.8 supply-chain compromise — the higher floor here covers that scenario as a side effect). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Two integration tests asserted the legacy spaced JSON body format
(`b'{"key": "value"}'`). Starting in httpx 0.28, the `json=...` arg is
serialized in compact form (`b'{"key":"value"}'`, no spaces) for wire
efficiency.
This caused:
1. test_forwarding_post_request: direct body assertion failure
(`b'{"key":"value"}' != b'{"key": "value"}'`)
2. test_forwarding_request_with_slack: 401 instead of 200, because the
test-side HMAC was computed over the spaced bytes while the server
verified against the compact bytes httpx actually sent
Both are test-side adaptations; runtime forwarding behavior is correct.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…llm-1.83.7-bump # Conflicts: # agentex/pyproject.toml # agentex/tests/integration/api/agent_api_keys/test_agent_api_keys_api.py # uv.lock
|
No reviewable files after applying ignore patterns. |
smoreinis
approved these changes
Apr 29, 2026
scale-ballen
changed the title
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
2 participants
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.
Summary
This PR now reflects the remaining effective diff after merging latest
main: a lockfile-only refresh. The LiteLLM vulnerability remediation originally described here has already landed through PR #209.Current change
uv.lock: updatesaiohttpfrom3.13.4to3.13.5and refreshes the associated package artifact hashes/URLs.Relationship to PR #209
PR #209 already landed the substantive AgentEx dependency vulnerability fixes:
litellm >=1.83.7,<2python-dotenv >=1.2.2,<2python-multipart >=0.0.26httpx[http2] >=0.28.1,<0.29workspace overrideBecause latest
mainalready includes those changes, this PR no longer carries the LiteLLM/security remediation itself.Verification
mainuv lock --lockedMerge note
Safe to merge as a small lockfile refresh, but it is no longer required for the LiteLLM vulnerability fix. That work is already present on
mainvia PR #209.