Skip to content

Version Packages (beta) - #9009

Merged
bokelley merged 1 commit into
mainfrom
changeset-release/main
Nov 17, 2026
Merged

bokelley merged 1 commit into
mainfrom
changeset-release/main

Conversation

@aao-release-bot

@aao-release-bot aao-release-bot Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

adcontextprotocol@3.3.0-rc.0

Minor Changes

  • 91f87f7: media_buy.audience_targeting no longer promises inline member push (Let audience_targeting say "no member push" now that supported_activation_methods exists, and say that discovery comes with audience_include #8936). Its presence now means the seller supports audience_include and audience_exclude in targeting overlays and answers discovery-only sync_audiences (called without audiences), which a declaring seller MUST do, so a buyer can always read the audience_id values it can target. Inline member push is declared by the sync_audiences pattern in the experimental audience_targeting.supported_activation_methods; when that field is absent, push is supported, as in 3.2. supported_identifier_types and minimum_audience_size move from required to an if/then that requires them only when the seller accepts inline push, so every capabilities document valid under 3.2 stays valid. A seller whose supported_activation_methods omits the sync_audiences pattern rejects, with UNSUPPORTED_FEATURE, a sync_audiences entry that carries add or remove or that would create a new audience without a source reference; source references for its declared rails still work. This lets an ad platform that can target the audiences already on an account, but cannot take a customer list, declare audience targeting without claiming member push. Generated types make both fields optional, and a strict 3.2 validator still requires them. Updated: get_adcp_capabilities, sync_audiences, the targeting guide, the 3.3 release notes and migration guide.

  • 145ba50: get_media_buy_delivery: the media_buy_deliveries[].by_package description now says sellers SHOULD return at least one row, one per package in the media buy, and SHOULD omit a buy's delivery row and return an error when the buy cannot be reported, rather than return an empty by_package. Every media buy has at least one package, and buyers price, cap and reconcile delivery per package. No schema constraint changes in 3.x: by_package: [] stays valid on the wire. Requiring at least one row (minItems: 1) is proposed for 4.0 in 4.0: require at least one by_package row in get_media_buy_delivery #8973.

  • 13060f6: Give three experimental 3.3 values the spelling their stable or sibling counterpart already uses (adcp#8901). Each was spelled two ways for one concept, and the side that changes is experimental, added in 3.3 and only in the 3.3 betas.

    This changes 3.3.0-beta.0 through beta.6; no stable release has these enums. The values are renamed in place, with no alias: they are experimental, and the additive-minor check compares against 3.2.x, which has none of the three files. The betas are immutable, so a seller or buyer built from a beta bundle sends and accepts the new spelling: readiness_status and the product rollup, creative.live_updates.in_place[].change, staged_update.change_kinds[] and the CREATIVE_LIVE_UPDATE_UNSUPPORTED details, and projection.projected_end_state. The training agent classifies creative changes with clickthrough.

    The consumed changesets for these features stay in .changeset/pre/ as history.

  • e88faeb: image_carousel gains an optional cta_values parameter (adcp#8960), the same shape as cta_values on native_in_feed and image. When it is declared, every card's cta MUST be one of the listed values, and a seller refuses any other value with CREATIVE_VALUE_NOT_ALLOWED, with error.field pointing at that card's cta. When it is absent, a card's cta takes free text and is not refused as CREATIVE_VALUE_NOT_ALLOWED. The card-asset cta description now names image_carousel cta_values as the governing set. Additive and optional: existing declarations are unchanged. Before 3.3 a carousel option could carry cta_values only as an undeclared parameter on the open params object.

    New optional compliance scenario media_buy_seller/declared_carousel_cta_values (3.3, gated on creative.has_creative_library). It seeds an image_carousel option that declares cta_values, expects sync_creatives to refuse a creative whose third card's cta is outside the set with CREATIVE_VALUE_NOT_ALLOWED, and expects the same creative with a declared value to be accepted.

  • f4899aa: Schema: add reserved-word-safe replacements for six enum positions that collide with SDK target languages, and deprecate the originals (Enum values collide with SDK target languages' reserved words and enum protocol — 16 positions, two of them unexpressable in Go and Java #8791). Each enum now accepts both spellings through 3.x; the original is deprecated in 3.3 and removed in 4.0.

    • pass → passed in enums/binary-verdict.json, get_media_buy_artifacts local_verdict, and the registry feed's compliance tracks status. pass is a Python keyword.
    • global → all in the RATE_LIMITED details scope. global is a Python keyword. The replacement is all, not agent, because enums/error-scope.json already defines agent as the calling buyer agent.
    • name → full_name in the signal definition onboarder.match_keys, on both core/signal-definition.json and core/signal-definition-enrichment.json. name collides with the enum member protocol in Python and Java.

    Each deprecated value is listed in x-deprecated-enum-values and carries deprecated: true, x-deprecated-in: "3.3.0", x-removed-in: "4.0.0", and x-superseded-by in a per-value enumMetadata entry. The 4.0 compatibility registry lists every site. Send a replacement only when the release served is 3.3 or later; a 3.2 receiver treats it as an unknown value. A published file, such as adagents.json, keeps the original through 3.x.

  • 15b0c46: Add Instagram, Facebook, Snapchat and X to distribution-identifier-type (adcp#8992), so a creator's social channels can be listed in collection.distribution[].identifiers and matched across sellers without falling back to platform_channel_id.

    Eight values, following the YouTube pattern: a stable ID is the canonical identifier, and a handle is a discovery alias that should resolve to it.

    • instagram_account_id and instagram_handle
    • facebook_page_id and facebook_page_handle
    • snapchat_profile_id and snapchat_handle
    • x_user_id and x_handle

    Registries compare handles case-insensitively, as @ plus the lowercased name, as they already do for youtube_channel_handle. The enum description notes the values were added in AdCP 3.3. Adding enum values is additive: every identifier list that accepts these values already accepted platform_channel_id, so nothing that validated before stops validating.

  • 01abd19: Sellers declare which sync_creatives assignment_operations they accept, and a refusal recommends replace only where the seller accepts it (adcp#8933). assign, unassign and replace have existed since 3.2 and 3.3 adds merge, but only merge had a capability flag, so a buyer learned what a seller accepted by being refused. Live creative updates made this matter: CREATIVE_LIVE_UPDATE_UNSUPPORTED told buyers to swap in a new creative with a replace that the seller might refuse too.

    • creative.assignment_operations. New optional array on get_adcp_capabilities, any of assign, unassign, replace and merge. The list is exact: the agent accepts every listed operation and rejects any other with UNSUPPORTED_FEATURE, applying nothing. Buyers MUST NOT send an operation that is not listed. Absent from a response served at 3.3 or later, the agent accepts none and buyers MUST NOT send assignment_operations. A response served at 3.2 cannot carry the field, so there its absence declares nothing.
    • Live updates require replace. An agent that declares the experimental creative.live_updates MUST list replace; the schema enforces it. The CREATIVE_LIVE_UPDATE_UNSUPPORTED recovery, suggestion and details say so. The CREATIVE_MERGE_REJECTED recovery and the content_mismatch and not_supported merge rejection reasons name replace only where the seller lists it.
    • Compact buys require assign. A seller that exposes buy_products or accept_proposal and declares creative.has_creative_library: true MUST list assign in a capabilities response served at 3.3 or later, because the compact lifecycle assigns creatives only through assignment_operations. A verifier constraint records it; the schema cannot, because the antecedent fields are 3.2 fields.
    • merge. Listing merge requires has_creative_library: true and stable_creative_ids: true, as supports_assignment_merge does. That flag stays for compatibility; when it is true, the list MUST include merge (schema-enforced), and a seller that lists merge SHOULD set it. The merge verifier capability gate now names the list.
    • Suggestions name only what the agent accepts. core/error.json suggestion: a suggestion, and the recovery a correctable code documents, SHOULD name only operations and fields the agent declares it accepts or the schema requires it to accept.
    • Conformance. media_buy_seller/assignment_replace_transfers_settings runs only against sellers that list assign and replace. media_buy_seller/compact_direct_buy_lifecycle checks that a seller with a creative library lists assign, and sales-broadcast-tv checks that the seller lists assign before sending one. The reference training agent lists assign, unassign and replace on its media-buy routes, refuses merge and every operation on its creative-only routes, and words its live-update refusal from its own list.

    Additive for schemas: a new optional capability field and description changes. Behaviorally, a 3.3 seller that accepts assignment_operations must now list them, or 3.3 buyers stop sending them.

  • ae585b5: Campaign governance (experimental governance.campaign): accept an omitted human_review_required, and state two sync_plans validation rules (adcp#8733, PR 3 of 3). This widens what sync-plans-request.json accepts and changes no plan_hash rule.

    • Omitted flag. A plan that declares a regulated policy category (fair_housing, fair_lending, fair_employment, pharmaceutical_advertising) or eu_ai_act_annex_iii, and omits human_review_required, is now schema-valid. The governance agent derives the flag from the plan's resolved policies and policy categories. Before, both then branches required the field, so the specification's "sets it automatically" could never apply. An explicit false is still rejected by const: true.
    • No schema default. "default": false is removed from human_review_required. A consumer that applied the default turned a valid omitted field into an explicit false, which the schema rejects. Schema default annotations are never applied to the plan_hash preimage, and a value the governance agent derives is not written into it.
    • Prose. The specification says the governance agent rejects, not overrides, a caller-supplied false. known-limitations and the trust page name the field the schema constrains.
    • Flight order. flight.end must be later than flight.start, else INVALID_REQUEST.
    • Policy ID uniqueness. An ID must not repeat in policy_ids, and a custom_policies[].policy_id must not equal an ID in policy_ids, else INVALID_REQUEST.

    The two validation rules are stated in prose and as x-adcp-validation annotations. The schema does not enforce them in 3.x; tightening it is deferred to 4.0 (adcp#8756). The plan-hash vector 004b gains a note that it exercises canonicalization only.

Patch Changes

  • d6c0f99: Align the inline submitted branches with their published async status files (adcp#8856). Eight tasks defined their submitted response twice, and the copies disagreed: the inline branch in <tool>-response.json rejected fields the published <tool>-async-response-submitted.json accepts, so the same response validated differently depending on which schema a validator used. The inline branches for sync_creatives (creatives, merges, warnings), build_creative (creative_manifest, creative_manifests, creatives, estimate), control_media_buy (media_buy_id, warnings), create_media_buy (media_buy_id, packages, warnings), sync_catalogs (catalogs, item_availability_states, item_availability_updates), and update_media_buy (media_buy_id, warnings) — plus the shared media-buy-commitment-response.json submitted branch behind accept_proposal and buy_products (media_buy_id, warnings) — no longer forbid those fields. Each fix is a recorded correction under DR-0036: the published status file already states the shape, and every value the inline branch accepted before still validates. To keep each response oneOf exclusive after that loosening, the success branches of create_media_buy, update_media_buy and build_creative also exclude a core/task-submitted.json body, so a submitted body carrying result fields matches the submitted branch only (the other tools' success branches already exclude it, by task_id/status or a fixed status: "completed"). The canonical warnings test (tests/relationship-scoped-indicators.test.cjs) follows the published files: its submitted-arm assertions now accept warnings on the submitted envelope (warnings stay excluded from error arms and from sync_creatives' success arm). No restructure: the bodies-only layout and generated unions stay in refactor(schemas): response schemas declare bodies only; generated status unions (discussion) #8565 for 4.0.

  • 3c0648f: media_buy_seller/audience_buy_flow runs its member push only for a seller that accepts inline member pushes (compliance: gate audience_buy_flow's member push on the seller accepting inline pushes (follow-up to #8936) #8998). The audience_binding, create_buy_with_audience and delivery_check phases are gated on media_buy.audience_targeting.supported_activation_methods being absent (the 3.2 meaning) or listing an entry whose pattern is sync_audiences. A 3.3 seller that declares audience_targeting without inline push (feat(schema): audience targeting without inline member push #8996) now grades those phases not_applicable instead of failing at the push, and still runs setup and the unbound-audience rejection. The gate uses the storyboard runner's any_of capability predicate and object-subset contains (feat(storyboard): any_of capability gates and object-subset contains adcp-client#3711), so the bundle needs an @adcp/sdk release that supports them.

  • 8d235c3: Clarify how a signing_keys pin combines when more than one authorized_agents[] entry in adagents.json matches the same agent (adcp#9016), for example an origin-only entry and an entry with the agent's full URL, or every entry at a Web Bot Auth signer's origin.

    • The rule counts only the entries that both match the agent and authorize the message's scope. Such an entry resolves to the property, is inside its effective window, and covers the country, collection and placement. An entry that authorizes nothing for the message neither pins nor unpins it.
    • Among those entries, the agent is pinned only if every one carries signing_keys. One of them with no signing_keys (absent or empty) leaves it unpinned.
    • When every one pins, the accepted keys are the union of their pins.
    • A message about several of the publisher's properties gets one pin per property, and the key must satisfy each, just as pins from different publishers intersect.
    • When copies of a pinned key differ in revoked_at, the earliest revoked_at applies, whatever the entry order.
    • On a shared host, one tenant's unpinned path entry does not affect another tenant. An unpinned origin-only entry affects every tenant.
    • The per-entry verifier MUST now reads "if the publisher pins the agent for the message's scope".
    • The directory's signing_keys_pinned is documented as a scope-agnostic summary that ignores entries outside their effective window.

    Updated:

    • docs/governance/property/adagents.mdx: Agent URL matching and signing_keys.
    • docs/building/by-layer/L1/security.mdx: Publisher pin precedence and Agent resolution step 3.
    • docs/reference/migration/agent-identity-3-3.mdx and docs/reference/migration/3-2-to-3-3.mdx.
    • docs/aao/directory-api.mdx.
    • The signing_keys and signing_keys_pinned descriptions in core/authorized-agent-base.json and aao/agent-publishers.json.
  • 75e84b7: Clarify what happens when more than one authorized_agents[] entry in adagents.json matches the same agent (adcp#8943), for example an origin-only entry and an entry with the agent's full URL: each matching entry authorizes the agent, and the agent's scope is the union of their scopes. A narrower entry never removes scope that another matching entry grants. Updated: the Agent URL matching section of docs/governance/property/adagents.mdx and the origin-only entry in docs/reference/migration/3-2-to-3-3.mdx.

  • 3acfa17: media_buy_seller/inline_creatives_without_sync: the product-scoped and publisher-scoped inline creatives carry format_option_ref, built from the captured declaration, so a seller that declares several options of the same format_kind can route them (adcp#8625). No schema changes.

  • 41d269f: Docs: state how buyers and sellers keep capability discovery working across releases. A buyer MUST send a prerelease adcp_version only to a peer whose supported_versions advertises that exact value, because a prerelease pin never negotiates down. A buyer SHOULD send discovery get_adcp_capabilities without a version pin, and on VERSION_UNSUPPORTED SHOULD retry without a pin or at a value from supported_versions, as the error code's recovery already says. A seller SHOULD serve get_adcp_capabilities without credentials; this becomes a MUST in 4.0. On MCP, a gateway or auth layer that allow-lists JSON-RPC methods SHOULD let server/discover (MCP 2026-07-28), initialize, and tools/list through without credentials, so current MCP clients don't treat the agent as requiring sign-in before they can read capabilities. Covered in Versioning, Authentication, the MCP guide, the 3.3 release docs, and the 4.0 compatibility page. No schema changes.

  • 620b161: Docs: the 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, the prerelease page, and Versions describe the reserved-word-safe enum replacements (feat(schema): add reserved-word-safe replacements for 6 enum positions and deprecate the originals (#8791) #8915) as part of 3.3.0-rc.0. pass becomes passed, global becomes all, and name becomes full_name in six positions. The originals are deprecated, not removed, and a replacement goes only to a peer served 3.3 or later.

  • 41d269f: Docs: bring the 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, the prerelease program page (formerly the beta program page, same URL), Versions, and the 3.3 rows of Choose your SDK to 3.3.0-rc.0. Adds rc.0 to the checkpoint and wire-pin tables, with the 3.3-rc documentation selector. Covers the 2026-11-09 decision to open the schemas that were closed by accident, and the closed-schema triage that followed it: which beta fields stay in 3.3, which leave because they sit on deprecated tasks or would extend the commercial terms held closed until 4.0, and which move. Records the boolean form of demographics as deprecated, and covers the other rc.0 changes (origin-only authorized_agents URLs, declared-option creative conformance, TMP cache isolation, the registry-policy capability, video containers, carousel card image sizes, and loosened URL patterns). Replaces the remaining "closed schemas stay closed" wording in the 3.1 to 3.2 guide, the optimization-reporting page, and the daily-budget spec. Deprecated 3.3 features are described as expected to be removed in 4.0, with 3.3 supported for at least 12 months after 4.0 GA, instead of a notice-period promise. The SDK guidance records @adcp/sdk 17.0.0-beta.22 and Python adcp 10.0.0b15 on beta.5, Python adcp 9.6.2 with the A2A input fix on the 3.2 line, no SDK on rc.0 yet, and no Go or Java support for 3.3. The in-review table reflects the 3.3.0 milestone as of 2026-11-10.

  • 6c34d90: Docs: the public test agent's opt-in 3.3 preview moves to 3.3-beta.6, the beta that @adcp/sdk 17.0.0-beta.24 and later and Python adcp 10.0.0b17 and later negotiate. The 3.3 beta program page and the quickstart name the new pin. The SDK guidance, the choose-your-SDK table and the release-notes checkpoint table record that @adcp/sdk 17.0.0-beta.24 and later bundle 3.3.0-beta.6, and that 17.0.0-beta.21 through 17.0.0-beta.23 and Python adcp 10.0.0b13 through 10.0.0b16 support beta.5.

@mintlify

mintlify Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
adcp 🟢 Ready View Preview Nov 16, 2026, 8:14 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: e88faeb
Prior ref: a8053a7
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43602661821
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot
aao-release-bot Bot force-pushed the changeset-release/main branch from a8053a7 to 293bb0a Compare November 14, 2026 14:08
@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: d6c0f99
Prior ref: 293bb0a
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43603790630
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 145ba50
Prior ref: ef4229e
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43609415707
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot
aao-release-bot Bot force-pushed the changeset-release/main branch from ef4229e to aefa1e8 Compare November 14, 2026 15:24
@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 75e84b7
Prior ref: aefa1e8
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43611133032
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot
aao-release-bot Bot force-pushed the changeset-release/main branch from aefa1e8 to cd1012c Compare November 14, 2026 15:44
@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: bbf10ef
Prior ref: cd1012c
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43613189853
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 8d235c3
Prior ref: 223abe4
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43643988512
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 3c0648f
Prior ref: 13fd18f
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43680473809
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot
aao-release-bot Bot force-pushed the changeset-release/main branch from 2d44364 to 13fd18f Compare November 15, 2026 05:25
@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Release PR changed or left Draft. Prior ref restored and verified.
Tested base: 3c0648f
Prior ref: 13fd18f
Candidate: 2d44364
Observed ref: 13fd18f
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43680473809
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Incomplete or previously quarantined action. Prior ref restored and verified.
Tested base: 3c0648f
Prior ref: 13fd18f
Candidate: 2d44364
Observed ref: 13fd18f
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43680473809
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 3acfa17
Prior ref: 13fd18f
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43730119341
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 454773a
Prior ref: e97eb1b
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43758632172
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 0206ab4
Prior ref: 9e5fb1f
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43762895856
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 484e3f5
Prior ref: 5d604e9
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43766942057
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: b300ec6
Prior ref: 7efc6ea
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43771249186
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 41d269f
Prior ref: b4017e1
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43874245499
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 36ee5f9
Prior ref: 8ecc0cb
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43897929321
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Changesets action did not complete successfully. Prior ref restored and verified.
Tested base: 36ee5f9
Prior ref: 8ecc0cb
Candidate: not pushed
Observed ref: 8ecc0cb
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43897929321
Do not mark Ready or merge without checking this run and fresh release provenance.

bokelley added a commit that referenced this pull request Nov 16, 2026
* docs(reference): describe #8915's reserved-word-safe enum replacements in the rc.0 docs

#8915 (f4899aa) merged after the rc.0 marker. It adds a replacement
for six enum positions that collide with SDK target languages and
deprecates the originals: pass to passed (binary-verdict,
local_verdict, the registry feed's compliance tracks status), global to
all (RATE_LIMITED scope), and name to full_name (signal onboarder
match_keys, on the definition and the enrichment). Both spellings are
valid through 3.x, and 4.0 removes the originals. Send a replacement
only to a peer served 3.3 or later; published files keep the original.

Add it to the rc.0 rows, the release-notes rc.0 bullet, status line and
deprecations, What's new, migration checklist row 61, a migration
section with old and new values, the send-only-to-3.3-peers table, and
the deprecations intro. #8915's v4-compatibility text is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(release): refresh the 3.3.0-rc.0 marker for #8915

#8915 (reserved-word-enum-replacements.md) merged after the rc.0 marker
(#9050), so the Release run's promote check would reject #9009 with
"Pending changesets do not match the reviewed RC promotion marker".
Regenerate .changeset/rc-promotion.json with npm run promote:rc --
--prepare. It folds all 17 pending changesets into 3.3.0-rc.0, each with
its sha256: the 15 #9050 listed, reserved-word-enum-replacements.md,
and this PR's rc0-docs-reserved-word-enums.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@aao-release-bot

Copy link
Copy Markdown
Contributor Author

HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft.
Tested base: 620b161
Prior ref: 8ecc0cb
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43941578665
Do not mark Ready or merge without checking this run and fresh release provenance.

@aao-release-bot
aao-release-bot Bot force-pushed the changeset-release/main branch from 8ecc0cb to 11ca6b1 Compare November 16, 2026 19:45
@bokelley
bokelley marked this pull request as ready for review November 16, 2026 20:41
@aao-secretariat

Copy link
Copy Markdown
Contributor

Ladon does not review bot-authored PRs.

@bokelley bokelley left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving 3.3.0-rc.0 at exact head 11ca6b1 on Brian's instruction: base = main tip 620b161, version/lockfile 3.3.0-rc.0, pre.json tag rc, 17 changesets consumed, artifacts and signed tarball present, CI green (70 checks).

🤖 Generated with Claude Code

@bokelley
bokelley merged commit b5ac0e1 into main Nov 17, 2026
70 checks passed
@bokelley
bokelley deleted the changeset-release/main branch November 17, 2026 01:44

This branch was successfully deployed

1 active deployment
staging — 11ca6b19 Deployed Nov 16, 2026 by mintlify[bot]
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