fix: pin a2a-sdk below 1.0 to prevent breaking changes#1145
Open
aidandaly24 wants to merge 1 commit intomainfrom
Open
fix: pin a2a-sdk below 1.0 to prevent breaking changes#1145aidandaly24 wants to merge 1 commit intomainfrom
aidandaly24 wants to merge 1 commit intomainfrom
Conversation
The a2a-python SDK recently released 1.0 with breaking protocol changes (0.3 spec -> 1.0 spec). Our A2A templates use 0.3-era APIs (a2a.server, a2a.types, a2a.utils) which are incompatible with the 1.0 release. Add an upper bound (< 1.0.0) to all three A2A template pyproject.toml files so pip resolves to 0.3.26 (latest compatible) instead of 1.0.x.
This was referenced May 6, 2026
|
Reviewed the diff — this looks good to merge. Verified:
No blocking issues. |
Contributor
Coverage Report
|
Hweinstock
approved these changes
May 6, 2026
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
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.
Description
The a2a-python SDK recently released v1.0.0 which upgrades from the 0.3 protocol spec to the 1.0 protocol spec. This introduces breaking changes to module paths and APIs that our A2A templates depend on (e.g.,
a2a.server.agent_execution,a2a.types,a2a.utils).Since our templates specify
a2a-sdk >= 0.2.0with no upper bound,pip installnow resolves to 1.0.x, breaking allagentcore create --protocol A2Aprojects.This PR adds
< 1.0.0upper bound to all three A2A templatepyproject.tomlfiles so pip resolves to 0.3.26 (latest compatible version).Files changed:
src/assets/python/a2a/googleadk/base/pyproject.tomlsrc/assets/python/a2a/strands/base/pyproject.tomlsrc/assets/python/a2a/langchain_langgraph/base/pyproject.tomlRelated Issue
Closes #1147
Documentation PR
N/A — no documentation changes needed.
Type of Change
Testing
How have you tested the change?
npm run test:unitandnpm run test:integnpm run typechecknpm run lintsrc/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.