Context
Tracking issue for all version-negotiation work that needs to land before 3.1 GA (~late June 2026). The spec change shipped via PR #3493; this epic tracks the downstream work that turns the spec into a usable contract for the ecosystem.
Work items
Done when
- All three SDKs (JS / Python / Go) emit
adcp_version on requests with adcp_major_version mirror.
- Compliance grader runs scenarios and reports presence as advisory.
- 3.1 GA ships with documented adopter path.
Related
Context
Tracking issue for all version-negotiation work that needs to land before 3.1 GA (~late June 2026). The spec change shipped via PR #3493; this epic tracks the downstream work that turns the spec into a usable contract for the ecosystem.
Work items
adcontextprotocol/adcp-client-python#294)VERSION_UNSUPPORTEDerror.@adcp/client.ComplianceIndextype bump — addpublished_version: stringto the TypeScript interface so consumers can read the preferred field. Until this lands, downstream code falls back to legacyadcp_versionalias via typed cast.adcp_versionrequest emission and response echo. Required to be in advisory mode at 3.1 per the migration table indocs/reference/versioning.mdx.adcp_versionrequest emit + response echo + capabilitiessupported_versions. Catches anything the spec PR didn't.bokelley/version-negotiation-rfcfrom origin (post-merge housekeeping).Done when
adcp_versionon requests withadcp_major_versionmirror.Related
6eadf0663)specs/version-negotiation.mddocs/reference/versioning.mdx