Skip to content

3.3.0 GA criteria and timeline #8600

Open

Description

@bokelley

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).

  • Published: 3.3.0-beta.0 (Oct 22), beta.1 (Oct 29), beta.2 (Oct 30), beta.3 (Oct 31), beta.4 (Nov 5).
  • Rolling betas: a new beta is cut whenever meaningful fixes land and main is green, at most about once a day.
  • GA-candidate beta: the week of Nov 16, after the Minor releases sometimes break older buyers, and our versioning rules disagree about whether that's allowed #8501 closed-schema triage lands. Its consent window closes Fri Nov 13.
  • 3.3.0 GA: the first beta that meets every criterion below. The target is the week of Nov 30, or the week of Nov 23 if everything passes first time.

GA criteria

  1. SDK support: the TypeScript (@adcp/sdk) and Python SDKs support the latest 3.3 beta. See adcp-client#3374 and adcp-client-python#1560.
  2. Storyboards green: the training-agent storyboard matrix passes, current and 3.0-compat, including the required-clean and required-exact lists.
  3. The closed-schema triage is complete (Minor releases sometimes break older buyers, and our versioning rules disagree about whether that's allowed #8501). Each 3.3 addition to a closed schema is moved to an open parent, recorded as a DR-0036 correction, or deferred to 4.0. The additive-minor baseline doesn't grow.
  4. No open objections on 3.3 consent items or decision records.
  5. Release docs are current: release notes, What's new, the migration guide and the 3.3 beta page match what's merged.

Experimental surfaces ship as experimental and don't need to graduate for GA.

Activity

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

    @bokelley
    ContributorAuthor

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

    Target: a GA-candidate beta in the week of Nov 16.

  3. bokelley commented on Oct 31, 2026

    @bokelley
    ContributorAuthor

    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
    ContributorAuthor

    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.

  5. bokelley commented on Nov 7, 2026

    @bokelley
    ContributorAuthor

    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:

    1. SDKs: met for beta.4 (@adcp/sdk 17.0.0-beta.19, Python adcp 10.0.0b12). This resets with each new beta.
    2. Storyboards: green on main.
    3. Closed-schema triage (Minor releases sometimes break older buyers, and our versioning rules disagree about whether that's allowed #8501): PRs are up for 22 of the 26 entries, and consent closes Nov 13.
    4. Objections: the docs(governance): DR-0032 and DR-0033, revised against DR-0036 #8519 objection is answered with a concession (docs(versioning): state the rules for what changes between releases #8704). DR-0036 goes to ratification at the Nov 9 session.
    5. Release docs: one beta behind. The final pass follows the GA-candidate beta.

    🤖 Generated with Claude Code

  6. bokelley commented on Nov 8, 2026

    @bokelley
    ContributorAuthor

    3.3.0-beta.5 is out. It's the fifth rolling 3.3 beta: two minor and four patch changes since beta.4 (Nov 5).

    New (experimental)

    Promoted

    • 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/sdk 17.0.0-beta.20 and Python adcp 10.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.

    Release: https://github.com/adcontextprotocol/adcp/releases/tag/v3.3.0-beta.5

    🤖 Generated with Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions