Skip to content

Bump websockets upper bound to allow v16 #5667

@Nabil-Salah

Description

@Nabil-Salah

** Please make sure you read the contribution guide and file the issues in the right place. **
Contribution guide.

🔴 Required Information

Is your feature request related to a specific problem?

adk-python's pyproject.toml currently pins websockets>=15.0.1,<16 (see pyproject.toml on main). This upper bound prevents downstream projects that depend on google-adk from upgrading websockets to v16.

Concretely, in the Jaeger project, Renovate raised a PR to bump websockets from >=15.0.1,<16.0.0 to >=16.0,<16.1.0 (jaegertracing/jaeger#8522). The lock-file update fails with:

Because google-adk>=1.28.1 depends on websockets>=15.0.1,<16.0.0 ... we can conclude that your project's requirements are unsatisfiable.

This is true for every released google-adk version through 1.33.0 and for main. There does not appear to be an open issue or PR tracking a websockets v16 bump in this repo.

Describe the Solution You'd Like

Widen the upper bound in pyproject.toml so v16 is permitted — e.g.:

- "websockets>=15.0.1,<16",  # For BaseLlmFlow
+ "websockets>=15.0.1,<17",  # For BaseLlmFlow

Metadata

Metadata

Assignees

Labels

core[Component] This issue is related to the core interface and implementationneeds review[Status] The PR/issue is awaiting review from the maintainer

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions