Skip to content

chore(deps): bump a2a-sdk lock to 1.2.0 - #44

Open
Superagentic-AI wants to merge 1 commit into
mainfrom
chore/a2a-sdk-1.2.0
Open

Superagentic-AI wants to merge 1 commit into
mainfrom
chore/a2a-sdk-1.2.0

Conversation

@Superagentic-AI

Copy link
Copy Markdown
Contributor

Summary

  • Lock optional a2a-sdk 1.1.2 → 1.2.0 (PyPI 2026-09-29 12:31 UTC). Extra pin is now >=1.2.0,<2.0.0.
  • Upstream 1.2.0 includes the previously watched InMemoryTaskStore timestamp fix (#1233), multi-replica cluster mode, agent-card caching headers, media-type validation, and stricter server validation.
  • Docs note + serve uhp docstring aligned to UHP 2026-09-12 (main client already negotiates that date).
  • Verified import of InMemoryTaskStore against installed a2a-sdk==1.2.0.

Supersedes #36 (stale 1.1.5 bump). Full uv lock OOMs on the ecosystem-watch box (exit 137 on the conflict matrix), so the lock package entry was updated surgically from PyPI hashes; CI should confirm resolution.

Ecosystem watch notes (not in this PR)

Test plan

  • CI green on this branch
  • Optional: uv sync --extra a2a resolves a2a-sdk==1.2.0

Adopt a2a-sdk 1.2.0 (PyPI 2026-09-29): InMemoryTaskStore timestamp
ordering (#1233), multi-replica cluster mode, agent-card caching
headers, and stricter server validation. Extra pin is now
>=1.2.0,<2.0.0. Align serve uhp docstring with client 2026-09-12.

Supersedes #36 (1.1.5).
@Superagentic-AI

Copy link
Copy Markdown
Contributor Author

Superseded by a fresh bump to a2a-sdk 1.2.1 (released 2026-09-30 11:52 UTC after this PR): see the new PR from chore/a2a-sdk-1.2.1 rebased on current main (2.4.38). This branch is stale vs main fixture/CI drift.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant