Repository navigation
fix(api): require patched JWT and HTTP dependencies - #853
Open
xianshijing-lk wants to merge 2 commits into
Open
xianshijing-lk wants to merge 2 commits into
xianshijing-lk wants to merge 2 commits into
Conversation
xianshijing-lk
requested review from
changt,
cloudwebrtc and
lukasIO
as code owners
October 9, 2026 14:26
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
…endencies # Conflicts: # uv.lock
This branch has not been deployed
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
1 participant
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.
Published livekit-api metadata permits old vulnerable PyJWT/aiohttp versions even when the workspace lockfile is updated. Require PyJWT >=2.15.1, aiohttp >=3.14.4 on Python 3.10+, and security floors for idna and multidict. Refresh both the root and local-video example lockfiles. Add a padded-signature regression test for the PyJWT 2.15.0 compatibility issue fixed in 2.15.1.
Preserve Python 3.9 support: it uses aiohttp >=3.13.5 and the last compatible multidict release. Their newer security fixes require Python 3.10+, so known aiohttp/multidict advisories remain on Python 3.9. This PR deliberately does not claim those findings are fixed. SDK users who need the complete HTTP dependency fixes must use Python 3.10+.
Expand API/failover CI to Python 3.9–3.14 and add built-wheel tests on Windows/macOS at the oldest/newest supported Python versions, with both minimum direct dependencies and current releases. Python 3.9 uses pytest 8.4.2 in an explicitly private temporary directory; modern test jobs use patched pytest.
Validation: built API/protocol wheels and sdists; 37 token/webhook/API/failover tests passed in each of 12 fresh environments (Python 3.9–3.14 × lowest-direct/highest); uv pip check passed in every environment; both mypy checks passed; Ruff passed. With the final runtime dependencies, all 163 RTC tests passed against a local LiveKit server (3 skips). The modern Python dependency scan reports no known vulnerabilities; Python 3.9 residual findings are documented above.
Land after the tooling PR. Supersedes the revision-only aiohttp PR #843 and the runtime/example updates from #711. Includes the PyJWT lock update from #841 if it has not landed already. Publish a livekit-api patch release after merging so consumers receive the new dependency requirements; no livekit or livekit-protocol release is required for these metadata changes.