fix: cap a2a-sdk<1.0 and @a2a-js/sdk<1.0.0 to avoid breaking 1.0 imports - #17
Merged
Conversation
…imports - Pin `a2a-sdk>=0.3.0,<1.0` in `python/pyproject.toml` so fresh installs no longer resolve to `a2a-sdk` 1.0.x, which renamed `A2AClient` to `Client` and broke `A2ASession`'s import in `a2a_utils.client.a2a_session`. - Regenerate `python/uv.lock` to resolve `a2a-sdk` 0.3.25. - Mirror the cap in `javascript/package.json` with `@a2a-js/sdk: ">=0.3.10 <1.0.0"` so a future `@a2a-js/sdk` 1.0 release cannot silently break `A2ASession` on the JavaScript side either. The explicit range also allows future 0.x minor bumps without dropping the upper bound. - Refresh `javascript/bun.lock` accordingly. - Fixes #16. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Merged
3 tasks
benclarkeio
added a commit
to a2anet/a2a-mcp
that referenced
this pull request
May 25, 2026
`a2anet-mcp` no longer imports anything from `a2a-sdk` directly — all SDK usage is transitive through `a2a_utils`. The `a2a-sdk>=0.3.21` line dated back to when `server.py` imported `AgentManager` and other `a2a.*` symbols directly, before they were moved into `a2a-utils`. - Remove `a2a-sdk>=0.3.21` from `dependencies` in `pyproject.toml` so `a2a-utils` is the single source of truth for the `a2a-sdk` version range. - Regenerate `uv.lock`. This also means downstream consumers will automatically pick up whatever `a2a-sdk` range `a2a-utils` declares, including the upcoming `<1.0` cap in `a2a-utils` 0.7.3 (a2anet/a2a-utils#17). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
a2a-sdk>=0.3.0,<1.0inpython/pyproject.tomlso fresh installs no longer resolve toa2a-sdk1.0.x, which renamedA2AClienttoClientand brokeA2ASession's import ina2a_utils.client.a2a_session.@a2a-js/sdk: ">=0.3.10 <1.0.0"injavascript/package.json, so a future@a2a-js/sdk1.0 release cannot silently breakA2ASessioneither. The explicit range also allows future 0.x minor bumps without dropping the upper bound.python/uv.lock(resolvesa2a-sdk0.3.25) andjavascript/bun.lock(resolves@a2a-js/sdk0.3.13).Fixes #16.
Test plan
uv run pytest— 222 passedbun test— 223 passedbun run typecheck— cleanuvx a2anet-mcp --helpworks against a downstream consumer that picks upa2a-utils0.7.3🤖 Generated with Claude Code