3.3.0 GA criteria and timeline #8600

Activity

1. bokelley

   added this to the 3.3.0 milestone on Oct 30, 2026
2. bokelley commented on Oct 31, 2026

   

   bokelley

   on Oct 31, 2026 – with conductor.build App

   ContributorAuthor

   More actions

   Status (2026-10-31), after 3.3.0-beta.3:

   • ✅ TypeScript SDK: @adcp/sdk 17.0.0-beta.6+ supports the 3.3 betas (adcp-client#3374 closed).
   • ⏳ Python SDK: adcp-client-python#1560 and fix: expose tagline field and harden XSS escaping in member directory #1680 are in progress.
   • ✅ Storyboards: green on main, apart from an intermittent runner-disk failure that's being re-run.
   • ⏳ Closed-schema triage: 26 entries are pending a disposition table on Minor releases sometimes break older buyers, and our versioning rules disagree about whether that's allowed #8501, for consent by Nov 13.
   • ⏳ Objections: the current async round closes Nov 6.
   • ⏳ Release docs: being refreshed through beta.3.

   Target: a GA-candidate beta in the week of Nov 16.
3. bokelley commented on Oct 31, 2026

   

   bokelley

   on Oct 31, 2026 – with conductor.build App

   ContributorAuthor

   More actions

   Python SDK: supports 3.3.0-beta.3. adcp-client-python 10.0.0-beta.5 (PEP 440 10.0.0b5) is tagged as a GitHub pre-release on the SDK's next line. It pins the signed, cosign-verified 3.3.0-beta.3 bundle, with get_supported_adcp_versions() of 3.0, 3.1, 3.2, 3.3-beta.3, 3.2-rc.7.

   Install:

   • from the tag, works now: pip install "adcp @ git+https://github.com/adcontextprotocol/adcp-client-python@v10.0.0-beta.5" (checked in a clean venv: package 10.0.0b5, spec 3.3.0-beta.3);
   • from PyPI: pip install --pre "adcp==10.0.0b5". The PyPI upload is waiting on the SDK's release-publish environment approval and is not live yet. I'll consider criterion 1 met for Python once it is. pip install adcp without --pre keeps resolving to the stable 9.x line (AdCP 3.2).

   What "supports" means here:

   • Types are generated from the published bundle, and every task response composes core/protocol-envelope.json (adcp#8547): status, task_id, timestamp, adcp_version, ... are inherited.
   • status is required on 3.3 responses and not sent under 3.2.x where that release's schema has none (list_products, decline_proposals). The served release's own schema decides, so a 3.2.x backport that composes the envelope needs no SDK change. This matches adcp-client#3493.
   • SDK tests: 20,880 passed, 0 failed on the branch; CI green on the merge into next.
   • Your "Generate Python SDK" job checks out next already. I reproduced it locally against the published bundle (key step, regenerate, validate-generated, tests/test_code_generation.py tests/test_schemas_version_pin.py: all pass). The real job builds from a protocol PR bundle, so that exact input wasn't run.

   Still open on the Python side, not blocking this: adcp-client-python#1680 asks to remove the schema-shaped generator patches (the async_response_refs side tree and class-keyed rewrites in post_generate_fixes.py). Generation works on beta.3 without that removal, and I have left the issue open for it.

   🤖 Generated with Claude Code
4. bokelley commented on Nov 1, 2026

   

   bokelley

   on Nov 1, 2026 – with conductor.build App

   ContributorAuthor

   More actions

   Release cadence (maintainer, 2026-11-01): 3.3 betas now roll continuously. One is cut whenever meaningful fixes land and main is green, so adopters can test early and often. GA is unchanged: it's the first beta that meets every criterion above. Release docs are refreshed in weekly batches, with a final pass before GA.