Repository navigation
Version Packages (rc) - #9073
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. |
|
HOLD: generated release branch requires human reconciliation/review. Changesets action did not complete successfully. Prior ref restored and verified. |
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
1b68765 to
588ff73
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
588ff73 to
55da8ac
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
55da8ac to
5f0108d
Compare
|
HOLD: generated release branch requires human reconciliation/review. Automation is preparing a leased update. The PR must remain Draft. |
5f0108d to
b46ec2e
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. |
|
Ladon does not review bot-authored PRs. |
The 3.3.0-rc.1 Version Packages head b46ec2e was generated on 61a1638 (#8736). #9080 merged afterwards without a changeset, so the bot never regenerated the PR, and #9073 was squash-merged as 32a90ee on base 5eb0b20 with a tree that differs from the reviewed head. Release run 44300240363 quarantined it at the provenance gate. Following RELEASING.md "Superseding an unpublishable committed prerelease", bind the committed candidate in a reviewed .changeset/release-supersession.json (release merge, committed tarball digest, reason, pending changeset pool), add the patch changeset that advances the line to 3.3.0-rc.2, and mark 3.3.0-rc.1 unpublished in the build, server and CDN worker release-status maps and the committed discovery index. The rc.1 schema, compliance and protocol bytes are unchanged. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.1
Minor Changes
61a1638: Add the experimental DOOH impression basis (
media_buy.dooh_impression_basis, RFC RFC: declare the DOOH impression basis — typed tier, effective multiplier, and derivation link, at delivery and discovery #7253). A DOOHimpressionsfigure isplays × audience multiplier, and the newenums/impression-estimation-basis.jsonsays where the multiplier comes from:currency_measured,seller_modeled,sensor_measuredorhybrid.dooh_metricscarriesimpression_basis,audience_multiplierandbasis_metric, thevendor_metric_values[]row a sensor audience comes from. A row mixing tiers reportsimpression_basis_breakdown[]instead: at least two entries with distinct tiers, summing exactly to the row, and no row-level tier or multiplier.venue_breakdown[]rows may carry the tier andplays, one per screen that played the spot, and no multiplier: a venue's audience per play is itsimpressions / plays.impression_basis,audience_multiplierandimpression_basis_breakdown[], outsidemetrics. A breakdown includes the fallback the seller expects.dooh_placement_attributescarries the planned tier and multiplier.impressionsis authoritative and the multiplier isimpressions / plays, rounded.hybridis a seller model calibrated by sensors on the seller's own screens, never a published currency nor a mix of tiers. All fields are optional.ooh_metrics.estimation_basisis unchanged.954eb9d: Campaign governance (experimental
governance.campaign): settle the rules the specification contradicted or left undefined (adcp#8733, PR 2 of 3). These are normative decisions of the Governance working group. No wire field, enum member orplan_hashrule changes. This is a change within the 3.3 pre-release.sync_plansthat reducesbudget.total(or a periodamount) below the amount already committed is rejected withVALIDATION_ERRORand leaves the plan unchanged. Before, the specification said the sync was accepted and flagged on the next check, while the task page said it was rejected.check_governance. A failedapproved_sellersordelegationsevaluation for an authenticated caller is returned as adeniedverdict with a finding and acheck_id, so the attempt can be audited. This holds in every governance mode. A plan is accessible to its owner principal, to a current delegate, and to a caller that presents agovernance_contextorconsultation_contextissued for that plan. Any other caller receivesPLAN_NOT_FOUND, the same response as for an unknownplan_id, and writes no audit entry. Before, the task page listedPERMISSION_DENIEDfor these cases.check_governancestill returnsPERMISSION_DENIEDwhen the caller is unauthenticated or its authenticated identity does not matchcaller. Callers that branch on the error code for the authority cases must also handle the verdict.approved: plans withhuman_review_required: trueescalate in every mode, and a failedapproved_sellersordelegationsevaluation isdeniedin every mode.plan_idnamespace. Aplan_idis unique per owner principal. Two principals may use the sameplan_id, and async_plansnever reads, changes or reveals another principal's plan.execute_only. A pre-approved action is one whose opaque action binding already holds an approved intent check in the plan's lifecycle. Anexecute_onlydelegate may act only on such an action, which includesaccept_proposalfor it. The governance agent MUST deny an intent check from anexecute_onlydelegate that would create a new binding or increase committed spend.conditionsnaming the region constraint, and an execution check returnsdenied.sync_plansreturnsREFERENCE_NOT_FOUNDwhen a registry policy ID inpolicy_idscannot be resolved.consultation_context.human_review_required: false. Thesync_planserror table states that it is rejected withVALIDATION_ERRORon a plan that requires human review.Training agent:
sync_plansnow rejects abudget.totalreduced below committed spend, andcheck_governancereturns thedeniedverdict for an authenticated execution caller that is not the audience preserved from the approved intent, and for a buyer-side caller whose delegation has ended. It no longer approves a failedapproved_sellersordelegationsevaluation in advisory or audit mode. For a plan that does not exist or that the caller cannot access,check_governancenow returns thePLAN_NOT_FOUNDerror; it returned adeniedverdict with aplan_lookupfinding.3a3bf1e: Withdraw
metric_idfrom performance standards and restore theevaluatorvalue ofx-entity-typesas deprecated (adcp#8501, entries 6 and 26). A minor release doesn't change what a signed term means or remove an existing enum value (DR-0036).metric_idon performance standards (feat(schema): name the vendor metric a performance standard is judged on #8436,3.3.0-beta.1through3.3.0-rc.0). Removed fromcore/canonical-performance-standard.json,core/performance-standard.jsonand therequired_performance_standardsentries ofcore/product-offer-filters.json, with the guard that kept it offviewabilityandcompletion_rate. The three schemas and theperformance-standard-metricdescription return to their 3.2.8 form. The field selects which vendor value decides a signed performance standard, so a 3.2 buyer would read the same standard differently. It is planned for 4.0 asperformance_standard_metric_id_required_in_4_0in the 4.0 compatibility registry, which keeps the design.evaluatorinx-entity-types. Restored with its definition and listed inx-deprecated-enum-values. The 3.2.8 versioning page says "Existing values are never removed or renamed." The removal of the experimentalevaluator_idsource form (feat(creative): remove experimental evaluator_id source form #8045) stands, so no 3.3 field carries the value.These are beta-to-beta changes, not changes to a stable release: 3.2.8 has no
metric_idon performance standards. The betas are immutable, so a seller or SDK built from a beta bundle stops sending and emitting the field.scripts/lint-additive-minor-baseline.jsondrops the two rows these entries covered and is now empty.Patch Changes
d24319d: Campaign governance (experimental
governance.campaign): follow-up errata found during the coherence sweep (adcp#8733, PR 4). Each edit follows a rule that is already stated elsewhere in the specification or schemas. No schema property, enum member orplan_hashrule changes.fair_housing,fair_lending,fair_employmentandpharmaceutical_advertisinginpolicy_categories, andeu_ai_act_annex_iiiinpolicy_ids. The FAQ no longer describes 3.0 in the future tense, and says that an omitted flag is accepted from 3.3.requires_human_reviewdescriptions inpolicy-category-definition.jsonandpolicy-entry.jsonsay the governance agent setsplan.human_review_required, as the specification does. The category description no longer says that a policy can override the category's setting: a policy adds the requirement and cannot remove it.budget.reallocation_thresholdis no longer documented as always required. The schema requires exactly one ofreallocation_thresholdorreallocation_unlimited: true, and thesync_plansfield table now lists both. The reallocation table and thereallocation_thresholddescription point toreallocation_unlimited: truefor unlimited reallocation, because a threshold equal tototaltightens whentotalchanges.approvedwith findings, and the "Execute" step and the image description no longer say budget is reserved.entries[].modedescription no longer refer to a closed issue or to mode as a plan property. Theentries[].modedescription no longer mentions agoverned_actions[].modefield that does not exist. The specification and the audit-trail page now state the same strength as the schema: a governance agent SHOULD record the mode on check entries, and outcome entries carry none.check_governanceresponse has carried an optionalmodeproperty since 3.1, and the task page documents it. The specification now says that mode is agent configuration, that no request carries it, and that the agent may report it on the response. Callers still MUST NOT branch on it.delegations[].expires_atdescription said that the governance agent denies an expired delegate's actions. It now follows the plan-access rule: a re-check that presents a context issued for the plan, and an execution check on an action the agent proposed, aredenied, and any other check from that agent returnsPLAN_NOT_FOUND.Training agent: the
modeproperty on itssync_planstool is described as a sandbox test control. Its behaviour is unchanged.c925886: Docs:
@adcp/sdk17.0.0-beta.29 and Pythonadcp10.0.0b20 bundle3.3.0-rc.0, and the public test agent's opt-in 3.3 preview moves to3.3-rc.0. Choose your SDK, the 3.3 prerelease page, the release notes, Versions, and the quickstart name the new versions and pin.@adcp/sdk17.0.0-beta.24 through 17.0.0-beta.28 and Pythonadcp10.0.0b17 through 10.0.0b19 support beta.6. The training agent's hosted preview is3.3-rc.0, validated against the published3.3.0-rc.0schemas.