fix(deps): update third party deps to v16#5833
Conversation
|
| dependencies = [ | ||
| "livekit-agents[codecs]>=1.5.8", | ||
| "websockets>=13.1,<16.0", | ||
| "websockets>=16,<16.1", |
There was a problem hiding this comment.
π΄ uv.lock not updated after websockets version bump β lock file is stale and inconsistent
The pyproject.toml was changed to require websockets>=16,<16.1, but the shared uv.lock file was not regenerated. The lock file still resolves websockets to version 15.0.1 and records the old specifier >=13.1,<16.0 for livekit-plugins-gnani. This means uv sync will detect a stale lock and fail (or silently use the wrong version), since 15.0.1 does not satisfy >=16,<16.1.
Stale lock file metadata
In uv.lock, the gnani entry still reads:
[package.metadata]
requires-dist = [
{ name = "websockets", specifier = ">=13.1,<16.0" },
]
And websockets is resolved globally to 15.0.1, which is incompatible with the new >=16,<16.1 requirement.
Prompt for agents
The pyproject.toml was updated to require websockets>=16,<16.1 but the root uv.lock was not regenerated. The lock file still resolves websockets to 15.0.1 and records the old specifier >=13.1,<16.0 for livekit-plugins-gnani. Run `uv lock` from the repository root to regenerate the lock file. Note that since this is a uv workspace with a single lock file, upgrading websockets to 16.x will affect all workspace members that depend on websockets (e.g. livekit-plugins-phonic, google-genai, fal-client, speechmatics-rt). Verify that all those packages are compatible with websockets 16.x before merging.
Was this helpful? React with π or π to provide feedback.
c5d66e7 to
8734c34
Compare
39431a4 to
75a73a5
Compare
Generated by renovateBot
75a73a5 to
b3664f4
Compare
This PR contains the following updates:
>=13.1,<16.0β>=16,<16.1Release Notes
python-websockets/websockets (websockets)
v16.0Compare Source
See https://websockets.readthedocs.io/en/stable/project/changelog.html for details.
Configuration
π Schedule: (UTC)
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.