You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposed release path and GA criteria for AdCP 3.3. Async consent: objections by Fri 2026-11-06, or raise them at the next working-group session, Mon 2026-11-09.
Release path
Updated 2026-11-07. Betas roll continuously (maintainer, 2026-11-01).
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.
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.
Consent closed (2026-11-07): no objections to these GA criteria by Fri Nov 6, so they stand as written. I've updated the release path above to reflect the rolling betas.
Where each criterion stands today:
SDKs: met for beta.4 (@adcp/sdk 17.0.0-beta.19, Python adcp 10.0.0b12). This resets with each new beta.
What a key declares:uid_type, an optional vendor, scopes, and uses: audience include or exclude, frequency capping, identity match and conversion attribution.
Where it appears: seller-wide as media_buy.supported_match_keys, per product as identity.match_keys, and on TMP provider registration.
Compatibility: two keys are compatible when they share a uid_type and a scope, and their vendors match when both declare one.
Rules: a product with no persistent identifier can't declare frequency-cap or identity-match keys.
sales-fixed-rate is now a stable specialism (DR-0028). The storyboard is unchanged and fully graded, and an independent fixed-price seller passes it, 19 of 19 steps. A passing claim now counts toward the AAO Verified media-buy badge.
Clarified
Public Suffix List (DR-0037). Verifiers compute eTLD+1 with a PSL bundled with the verifier, never fetched at runtime. AdCP names no reference snapshot. On the trust-record path, a verifier missing a newly added PRIVATE suffix fails closed.
Conformance and tooling
deterministic_testing storyboard: it now pins its fixtures and controller calls to one sandbox account, so lifecycle controls can't target the wrong account.
Legacy creative fixtures: there's a gated, offline test-kit catalog for them, with exact format references and no Creative Protocol requirement for media-buy-only sellers.
Storyboard CI: it fetches historical files on demand, which unblocks protocol conformance runs.
SDKs:@adcp/sdk17.0.0-beta.20 and Python adcp10.0.0b12 support beta.4; adoption of beta.5 follows. Pin "3.2" for production traffic.
Coming next: the #8501 closed-schema triage lands after its consent closes on Nov 13, and the GA-candidate beta follows in the week of Nov 16.
Activity
bokelley commentedon Oct 31, 2026
Status (2026-10-31), after
3.3.0-beta.3:@adcp/sdk17.0.0-beta.6+ supports the 3.3 betas (adcp-client#3374 closed).main, apart from an intermittent runner-disk failure that's being re-run.Target: a GA-candidate beta in the week of Nov 16.
bokelley commentedon Oct 31, 2026
Python SDK: supports
3.3.0-beta.3. adcp-client-python10.0.0-beta.5(PEP 44010.0.0b5) is tagged as a GitHub pre-release on the SDK'snextline. It pins the signed, cosign-verified3.3.0-beta.3bundle, withget_supported_adcp_versions()of3.0, 3.1, 3.2, 3.3-beta.3, 3.2-rc.7.Install:
pip install "adcp @ git+https://github.com/adcontextprotocol/adcp-client-python@v10.0.0-beta.5"(checked in a clean venv: package10.0.0b5, spec3.3.0-beta.3);pip install --pre "adcp==10.0.0b5". The PyPI upload is waiting on the SDK'srelease-publishenvironment approval and is not live yet. I'll consider criterion 1 met for Python once it is.pip install adcpwithout--prekeeps resolving to the stable 9.x line (AdCP 3.2).What "supports" means here:
core/protocol-envelope.json(adcp#8547):status,task_id,timestamp,adcp_version, ... are inherited.statusis 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.next.nextalready. 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_refsside tree and class-keyed rewrites inpost_generate_fixes.py). Generation works on beta.3 without that removal, and I have left the issue open for it.🤖 Generated with Claude Code
bokelley commentedon Nov 1, 2026
Release cadence (maintainer, 2026-11-01): 3.3 betas now roll continuously. One is cut whenever meaningful fixes land and
mainis 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.bokelley commentedon Nov 7, 2026
Consent closed (2026-11-07): no objections to these GA criteria by Fri Nov 6, so they stand as written. I've updated the release path above to reflect the rolling betas.
Where each criterion stands today:
@adcp/sdk17.0.0-beta.19, Pythonadcp10.0.0b12). This resets with each new beta.main.🤖 Generated with Claude Code
bokelley commentedon Nov 8, 2026
3.3.0-beta.5is out. It's the fifth rolling 3.3 beta: two minor and four patch changes since beta.4 (Nov 5).New (experimental)
uid_type, an optional vendor, scopes, and uses: audience include or exclude, frequency capping, identity match and conversion attribution.media_buy.supported_match_keys, per product asidentity.match_keys, and on TMP provider registration.uid_typeand a scope, and their vendors match when both declare one.media_buy.match_keysexperimental feature. It stays experimental at 3.3 GA; the conformance coverage graduation needs is Conformance coverage for match keys before graduating media_buy.match_keys #8451.Promoted
sales-fixed-rateis now a stable specialism (DR-0028). The storyboard is unchanged and fully graded, and an independent fixed-price seller passes it, 19 of 19 steps. A passing claim now counts toward the AAO Verified media-buy badge.Clarified
Conformance and tooling
deterministic_testingstoryboard: it now pins its fixtures and controller calls to one sandbox account, so lifecycle controls can't target the wrong account.SDKs:
@adcp/sdk17.0.0-beta.20and Pythonadcp10.0.0b12support beta.4; adoption of beta.5 follows. Pin"3.2"for production traffic.Coming next: the #8501 closed-schema triage lands after its consent closes on Nov 13, and the GA-candidate beta follows in the week of Nov 16.
Release: https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.5
🤖 Generated with Claude Code