Repository navigation
Version Packages (beta) - #9009
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
a8053a7 to
293bb0a
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
293bb0a to
ef4229e
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
ef4229e to
aefa1e8
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
aefa1e8 to
cd1012c
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
cd1012c to
223abe4
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
223abe4 to
13fd18f
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
2d44364 to
13fd18f
Compare
|
HOLD: generated release branch requires human reconciliation/review. Release PR changed or left Draft. Prior ref restored and verified. |
|
HOLD: generated release branch requires human reconciliation/review. Incomplete or previously quarantined action. Prior ref restored and verified. |
13fd18f to
2d44364
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
13fd18f to
e97eb1b
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
e97eb1b to
9e5fb1f
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
9e5fb1f to
5d604e9
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
5d604e9 to
7efc6ea
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
7efc6ea to
b4017e1
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
b4017e1 to
8ecc0cb
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
|
HOLD: generated release branch requires human reconciliation/review. Changesets action did not complete successfully. Prior ref restored and verified. |
* 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>
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
8ecc0cb to
11ca6b1
Compare
|
Ladon does not review bot-authored PRs. |
bokelley
left a comment
There was a problem hiding this comment.
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
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
adcontextprotocol@3.3.0-rc.0
Minor Changes
91f87f7:
media_buy.audience_targetingno longer promises inline member push (Letaudience_targetingsay "no member push" now thatsupported_activation_methodsexists, and say that discovery comes withaudience_include#8936). Its presence now means the seller supportsaudience_includeandaudience_excludein targeting overlays and answers discovery-onlysync_audiences(called withoutaudiences), which a declaring seller MUST do, so a buyer can always read theaudience_idvalues it can target. Inline member push is declared by thesync_audiencespattern in the experimentalaudience_targeting.supported_activation_methods; when that field is absent, push is supported, as in 3.2.supported_identifier_typesandminimum_audience_sizemove fromrequiredto anif/thenthat requires them only when the seller accepts inline push, so every capabilities document valid under 3.2 stays valid. A seller whosesupported_activation_methodsomits thesync_audiencespattern rejects, withUNSUPPORTED_FEATURE, async_audiencesentry that carriesaddorremoveor that would create a new audience without asourcereference;sourcereferences 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: themedia_buy_deliveries[].by_packagedescription 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 emptyby_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.
enums/execution-readiness-status.json(media_buy.execution_readiness, feat(schema): add experimental per-account execution readiness #7934, beta.1 to beta.6):input_requiredbecomesinput-required, the spelling ofenums/task-status.json, which follows A2A's task states.enums/creative-change-kind.json(creative.live_updates, feat(creative): live creative updates with staged activation (experimental) #8488, beta.3 to beta.6):click_throughbecomesclickthrough, theurl_typevalue the change kind names inenums/url-asset-type.json.enums/delivery-projection-end-state.json(media_buy.delivery_projection, feat(schema): add optional delivery projection to get_media_buy_delivery packages #8043, beta.0 to beta.6):underdeliverybecomesunder_delivery, the spelling ofenums/offer-reason.json. DR-0029 is amended to the new spelling.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_statusand the product rollup,creative.live_updates.in_place[].change,staged_update.change_kinds[]and theCREATIVE_LIVE_UPDATE_UNSUPPORTEDdetails, andprojection.projected_end_state. The training agent classifies creative changes withclickthrough.The consumed changesets for these features stay in
.changeset/pre/as history.e88faeb:
image_carouselgains an optionalcta_valuesparameter (adcp#8960), the same shape ascta_valuesonnative_in_feedandimage. When it is declared, every card'sctaMUST be one of the listed values, and a seller refuses any other value withCREATIVE_VALUE_NOT_ALLOWED, witherror.fieldpointing at that card'scta. When it is absent, a card'sctatakes free text and is not refused asCREATIVE_VALUE_NOT_ALLOWED. Thecard-assetctadescription now namesimage_carouselcta_valuesas the governing set. Additive and optional: existing declarations are unchanged. Before 3.3 a carousel option could carrycta_valuesonly as an undeclared parameter on the openparamsobject.New optional compliance scenario
media_buy_seller/declared_carousel_cta_values(3.3, gated oncreative.has_creative_library). It seeds animage_carouseloption that declarescta_values, expectssync_creativesto refuse a creative whose third card'sctais outside the set withCREATIVE_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→passedinenums/binary-verdict.json,get_media_buy_artifactslocal_verdict, and the registry feed's compliancetracksstatus.passis a Python keyword.global→allin theRATE_LIMITEDdetailsscope.globalis a Python keyword. The replacement isall, notagent, becauseenums/error-scope.jsonalready definesagentas the calling buyer agent.name→full_namein the signal definitiononboarder.match_keys, on bothcore/signal-definition.jsonandcore/signal-definition-enrichment.json.namecollides with the enum member protocol in Python and Java.Each deprecated value is listed in
x-deprecated-enum-valuesand carriesdeprecated: true,x-deprecated-in: "3.3.0",x-removed-in: "4.0.0", andx-superseded-byin a per-valueenumMetadataentry. 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 asadagents.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 incollection.distribution[].identifiersand matched across sellers without falling back toplatform_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_idandinstagram_handlefacebook_page_idandfacebook_page_handlesnapchat_profile_idandsnapchat_handlex_user_idandx_handleRegistries compare handles case-insensitively, as
@plus the lowercased name, as they already do foryoutube_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 acceptedplatform_channel_id, so nothing that validated before stops validating.01abd19: Sellers declare which
sync_creativesassignment_operationsthey accept, and a refusal recommendsreplaceonly where the seller accepts it (adcp#8933).assign,unassignandreplacehave existed since 3.2 and 3.3 addsmerge, but onlymergehad a capability flag, so a buyer learned what a seller accepted by being refused. Live creative updates made this matter:CREATIVE_LIVE_UPDATE_UNSUPPORTEDtold buyers to swap in a new creative with areplacethat the seller might refuse too.creative.assignment_operations. New optional array onget_adcp_capabilities, any ofassign,unassign,replaceandmerge. The list is exact: the agent accepts every listed operation and rejects any other withUNSUPPORTED_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 sendassignment_operations. A response served at 3.2 cannot carry the field, so there its absence declares nothing.replace. An agent that declares the experimentalcreative.live_updatesMUST listreplace; the schema enforces it. TheCREATIVE_LIVE_UPDATE_UNSUPPORTEDrecovery, suggestion and details say so. TheCREATIVE_MERGE_REJECTEDrecovery and thecontent_mismatchandnot_supportedmerge rejection reasons namereplaceonly where the seller lists it.assign. A seller that exposesbuy_productsoraccept_proposaland declarescreative.has_creative_library: trueMUST listassignin a capabilities response served at 3.3 or later, because the compact lifecycle assigns creatives only throughassignment_operations. A verifier constraint records it; the schema cannot, because the antecedent fields are 3.2 fields.merge. Listingmergerequireshas_creative_library: trueandstable_creative_ids: true, assupports_assignment_mergedoes. That flag stays for compatibility; when it istrue, the list MUST includemerge(schema-enforced), and a seller that listsmergeSHOULD set it. Themergeverifier capability gate now names the list.core/error.jsonsuggestion: 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.media_buy_seller/assignment_replace_transfers_settingsruns only against sellers that listassignandreplace.media_buy_seller/compact_direct_buy_lifecyclechecks that a seller with a creative library listsassign, andsales-broadcast-tvchecks that the seller listsassignbefore sending one. The reference training agent listsassign,unassignandreplaceon its media-buy routes, refusesmergeand 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_operationsmust now list them, or 3.3 buyers stop sending them.ae585b5: Campaign governance (experimental
governance.campaign): accept an omittedhuman_review_required, and state twosync_plansvalidation rules (adcp#8733, PR 3 of 3). This widens whatsync-plans-request.jsonaccepts and changes noplan_hashrule.fair_housing,fair_lending,fair_employment,pharmaceutical_advertising) oreu_ai_act_annex_iii, and omitshuman_review_required, is now schema-valid. The governance agent derives the flag from the plan's resolved policies and policy categories. Before, boththenbranches required the field, so the specification's "sets it automatically" could never apply. An explicitfalseis still rejected byconst: true."default": falseis removed fromhuman_review_required. A consumer that applied the default turned a valid omitted field into an explicitfalse, which the schema rejects. Schemadefaultannotations are never applied to theplan_hashpreimage, and a value the governance agent derives is not written into it.false.known-limitationsand the trust page name the field the schema constrains.flight.endmust be later thanflight.start, elseINVALID_REQUEST.policy_ids, and acustom_policies[].policy_idmust not equal an ID inpolicy_ids, elseINVALID_REQUEST.The two validation rules are stated in prose and as
x-adcp-validationannotations. The schema does not enforce them in 3.x; tightening it is deferred to 4.0 (adcp#8756). The plan-hash vector004bgains a note that it exercises canonicalization only.Patch Changes
d6c0f99: Align the inline
submittedbranches 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.jsonrejected fields the published<tool>-async-response-submitted.jsonaccepts, so the same response validated differently depending on which schema a validator used. The inline branches forsync_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), andupdate_media_buy(media_buy_id, warnings) — plus the sharedmedia-buy-commitment-response.jsonsubmitted branch behindaccept_proposalandbuy_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 responseoneOfexclusive after that loosening, the success branches ofcreate_media_buy,update_media_buyandbuild_creativealso exclude acore/task-submitted.jsonbody, so a submitted body carrying result fields matches the submitted branch only (the other tools' success branches already exclude it, bytask_id/statusor a fixedstatus: "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 fromsync_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_flowruns 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). Theaudience_binding,create_buy_with_audienceanddelivery_checkphases are gated onmedia_buy.audience_targeting.supported_activation_methodsbeing absent (the 3.2 meaning) or listing an entry whosepatternissync_audiences. A 3.3 seller that declaresaudience_targetingwithout inline push (feat(schema): audience targeting without inline member push #8996) now grades those phasesnot_applicableinstead of failing at the push, and still runs setup and the unbound-audience rejection. The gate uses the storyboard runner'sany_ofcapability predicate and object-subsetcontains(feat(storyboard): any_of capability gates and object-subset contains adcp-client#3711), so the bundle needs an@adcp/sdkrelease that supports them.8d235c3: Clarify how a
signing_keyspin combines when more than oneauthorized_agents[]entry inadagents.jsonmatches 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.signing_keys. One of them with nosigning_keys(absent or empty) leaves it unpinned.revoked_at, the earliestrevoked_atapplies, whatever the entry order.signing_keys_pinnedis documented as a scope-agnostic summary that ignores entries outside their effective window.Updated:
docs/governance/property/adagents.mdx: Agent URL matching andsigning_keys.docs/building/by-layer/L1/security.mdx: Publisher pin precedence and Agent resolution step 3.docs/reference/migration/agent-identity-3-3.mdxanddocs/reference/migration/3-2-to-3-3.mdx.docs/aao/directory-api.mdx.signing_keysandsigning_keys_pinneddescriptions incore/authorized-agent-base.jsonandaao/agent-publishers.json.75e84b7: Clarify what happens when more than one
authorized_agents[]entry inadagents.jsonmatches 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 ofdocs/governance/property/adagents.mdxand the origin-only entry indocs/reference/migration/3-2-to-3-3.mdx.3acfa17:
media_buy_seller/inline_creatives_without_sync: the product-scoped and publisher-scoped inline creatives carryformat_option_ref, built from the captured declaration, so a seller that declares several options of the sameformat_kindcan 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_versiononly to a peer whosesupported_versionsadvertises that exact value, because a prerelease pin never negotiates down. A buyer SHOULD send discoveryget_adcp_capabilitieswithout a version pin, and onVERSION_UNSUPPORTEDSHOULD retry without a pin or at a value fromsupported_versions, as the error code's recovery already says. A seller SHOULD serveget_adcp_capabilitieswithout credentials; this becomes a MUST in 4.0. On MCP, a gateway or auth layer that allow-lists JSON-RPC methods SHOULD letserver/discover(MCP2026-07-28),initialize, andtools/listthrough 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.passbecomespassed,globalbecomesall, andnamebecomesfull_namein 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 the3.3-rcdocumentation 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 ofdemographicsas deprecated, and covers the other rc.0 changes (origin-onlyauthorized_agentsURLs, 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/sdk17.0.0-beta.22 and Pythonadcp10.0.0b15 on beta.5, Pythonadcp9.6.2 with the A2Ainputfix 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/sdk17.0.0-beta.24 and later and Pythonadcp10.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/sdk17.0.0-beta.24 and later bundle3.3.0-beta.6, and that 17.0.0-beta.21 through 17.0.0-beta.23 and Pythonadcp10.0.0b13 through 10.0.0b16 support beta.5.