Skip to content

Version Packages (beta) - #8801

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

bokelley merged 1 commit into
mainfrom
changeset-release/main

Conversation

@aao-release-bot

@aao-release-bot aao-release-bot Bot commented Nov 8, 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-beta.6

Minor Changes

  • b7907ee: An origin-only authorized_agents[].url in adagents.json now authorizes the agent at that origin, whatever its path (adcp#8862). An entry whose canonical form has the root path and no query, such as https://agent.example.com, matches any agent URL with the same canonical origin, including https://agent.example.com/mcp. An entry with a path still matches only that canonical URL, so path-mounted agents on a shared host stay distinct. This aligns adagents.json with the accepted DR-0023 (an agent's identity is its origin, one agent per origin), under which authorized_agents[].url already matched a Web Bot Auth signer by canonical origin. Matching only widens: no entry that authorized an agent under 3.2 stops authorizing it. Validators, TMP providers and registries that check authorized_agents[].url must apply the origin-only rule. Updated: docs/reference/url-canonicalization.mdx, the Agent URL matching section of docs/governance/property/adagents.mdx, the TMP sync-time validation, the authorized-agent-base.json url description, both 3.3 migration guides, and R0 in specs/agent-identity-3-3.md.

  • 7dd93fe: Move the experimental available_installment_statuses (media_buy.installment_lifecycle, feat(schema): installment lifecycle and proof of publication on by_installment rows #8116) from core/reporting-capabilities.json to core/canonical-reporting-capabilities.json (adcp#8501). The definition, x-status: experimental and x-added-in: 3.3.0 are unchanged.

    core/reporting-capabilities.json is used only by the deprecated get_products product, and 3.3 adds no field that exists only on a deprecated task. The canonical product's reporting capabilities, returned by list_products, request_proposals and refine_proposals, already carry supports_installment_breakdown, and the opened schema (DR-0036) now takes the status list beside it.

    This changes 3.3.0-beta.0 through beta.5. The betas are immutable. A seller built from one declares available_installment_statuses on the canonical product's reporting_capabilities and stops sending it on a get_products product. The installment lifecycle docs and experimental status page say where it lives.

  • 49c7231: Keep core/sla-window.json at its 3.2.8 shape and move business time onto the creative review SLA (adcp#8501, entries 11 and 12). sla-window stays closed with the commercial terms until 4.0 (DR-0036), and 3.3.0-beta.1 added clock and business_calendar_id to it, so a strict 3.2 validator rejected a 3.3 SLA. The signed terms use sla-window through change_terms[].processing_sla, and 3.2.8 says sellers include weekends and non-working periods in the maximum, so the signed SLA stays elapsed time.

    clock and business_calendar_id now live on core/creative-review-sla.json. creative_policy.review_sla keeps business time: clock defaults to elapsed, clock: "business" requires a business_calendar_id that resolves to get_adcp_capabilities.business_calendars[], and the calendar and snapshot rules are unchanged. The schema no longer composes sla-window. It defines response_max and completion_max itself, keeps completion_max required, and is open.

    Every other SLA is elapsed time, as in 3.2. An action's sla on allowed_actions[] and available_actions[], a change term's processing_sla, and core/escalation-sla.json reject clock and business_calendar_id. escalation-sla loses the clock: "elapsed" it accepted in the betas.

    This changes 3.3.0-beta.1 through beta.5. The betas are immutable. A seller or SDK built from one stops sending clock and business_calendar_id anywhere except creative_policy.review_sla and the review_sla on a creative action. The 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, and the service commitments page are updated.

  • db87715: Add the optional creative.supports_registry_policy_enforcement capability and
    gate the creative/policy_backed_rejections storyboard on explicit support, so
    sellers that do not publish registry policies in enforced_policies report that
    coverage as not applicable instead of failing it. A creative library alone does
    not imply support, and a seller that publishes a policy must still enforce it.
    The reference seller advertises the flag on the 3.3 contract.

  • aa94f36: Targeting can carry display names beside its geographic codes. core/targeting.json adds geo_value_labels, a map from the ISO codes in geo_countries, geo_countries_exclude, geo_regions and geo_regions_exclude to their names ({ "DE": "Germany", "US-CA": "California" }), and core/targeting-input.json accepts it. core/geo-metro.json and the geo_metros_exclude entries add value_labels, the shape geo_places already uses ({ "501": "New York" }). Every label key must appear in the values it labels, which conformance tooling enforces through x-adcp-validation. Labels are not a targeting dimension: sellers never resolve or apply targeting from them, never reject a request because they are present, and may omit, keep or supply their own in readback, and targeting equality and exact readback compare codes only. A name in place of a code is still invalid. This lets a package, proposal or audit log show "New York" next to 501 without a separate lookup. Buyers should not send geo_value_labels to a seller on a version before 3.3. Updated: the Geographic Restrictions section of the targeting guide.

  • 3cf5f53: image_carousel gains an optional card_image_sizes parameter (adcp#8911): a list of accepted logical { width, height } pairs for card images, the same shape as native_in_feed's main_image_sizes. Each image card's media must match one listed pair exactly; a larger image at the same ratio does not match. When the cards slot declares pixel_ratios, the intrinsic size is the matched pair times the selected ratio. All card images in one creative match pairs of the same aspect ratio. The field does not constrain video card media. When card_aspect_ratio is also declared, every listed pair must have that ratio within 1%; a declaration where they disagree is invalid. Additive and optional: existing declarations are unchanged, and a seller that omits the field leaves card pixel size unconstrained beyond card_aspect_ratio.

  • e903ee6: Add experimental installment_refs to the assign and replace operations of sync_creatives assignment_operations (media_buy.installment_creative_assignment, RFC: Assign a creative to specific installments of a package #8968). A buyer can now give each installment of a package its own creative, such as the awareness brief on a creator's first post and the offer on the second. Each entry is a core/canonical-installment-ref.json, with unique items and at most 500, matching a product's installments. Absent means every installment, as before.

    • Rotation. Within one installment, weight, rotation and placement routing work unchanged over the assignments that apply to it. Placement routing and installment scope intersect. An installment no assignment applies to gets no creative scoped to another installment.
    • Seller rules. Each ref MUST name an installment in the installments of the purchased product. Any other ref is rejected with VALIDATION_ERROR. An operation that changes an installment past its deadlines.change_cutoff is rejected with CREATIVE_DEADLINE_EXCEEDED, naming the installment, and is never accepted silently. No new error codes.
    • Scope changes. A supplied list replaces the assignment's scope, and omission on an assign upsert keeps it. replace transfers the replaced assignment's scope unless it supplies one, and merge moves it. unassign and merge reject installment_refs by name.
    • Readback. The same field appears on get_media_buys packages[].creative_approvals[] and list_creatives assignments.assigned_packages[], and is omitted when the assignment applies to every installment.
    • Capability. Buyers send the field only to sellers that list media_buy.installment_creative_assignment in experimental_features, because a seller that ignored it would run the creative on every installment (versioning rule 4). A seller that does not support it rejects it with UNSUPPORTED_FEATURE.

    The field is not on core/creative-assignment.json, the deprecated create_media_buy and update_media_buy package rows, or the deprecated sync_creatives assignments[] row. 3.3 adds nothing to deprecated tasks (Minor releases sometimes break older buyers, and our versioning rules disagree about whether that's allowed #8501). Date windows (valid_from / valid_until) for packages without installments are a follow-up.

  • a7af517: Choose specific installments through refine_proposals (experimental, media_buy.installment_refinement, adcp#8967).

    A buyer sends installment_changes, a list of { product_id, installment_ref, action } entries unique by (product_id, installment_ref). installment_ref is the closed core/canonical-installment-ref.json, and action is include or omit. The seller answers with a draft that buys, for each named product, one product whose installments[] is exactly the selected set. That's the named product's installments with every omit removed and every include added, often in a product the seller derives for the selection. Entries a seller can't satisfy come back in unsatisfied_installment_changes on the result row, each with a reason, on a partial or unable result with reason_code: "constraint_unsatisfiable".

    Nothing in commercial_terms changes. Buying a product still buys its complete installment set, so terms_digest binds the choice through the product_id. Three rules make that hold:

    • A seller MUST NOT change the installments of a product it has offered; a different set is a different product_id.
    • The buyer compares each selected set with the returned product's installments[] and rejects a mismatch.
    • The seller checks product membership before it resolves any installment reference.

    A seller that supports it lists media_buy.installment_refinement in experimental_features and installment_changes in media_buy.proposal_refinement.supported_dimensions, and the capabilities schema requires the first whenever the second is present. Buyers send installment_changes only to such a seller. This is a new feature id. media_buy.installment_selection, which named the signed purchases[].installments[] withdrawn after beta.1, stays withdrawn, and 4.0 keeps that design (installment_selection_required_in_4_0).

    New schemas: core/installment-change.json and core/installment-change-set.json. Every new field is x-status: experimental and x-added-in: 3.3.0. The training agent doesn't implement it yet.

  • 2dc672e: Open the schemas that were meant to be open (working-group decision of 2026-11-09, DR-0036). Closing a schema only breaks validators that hard-code it, so opening one is not a protocol break.

    additionalProperties goes from false to true at 747 of the 859 closed locations in the 3.3 source. Nothing else in those schemas changes, and every payload that was valid stays valid. This includes the capability blocks and containers that fix(schemas): open the capability blocks and containers 3.3 extends, against DR-0019 (#8501) #8772 opened (daypart windows, the targeting overlay requirement and support containers, and the spot and canonical reporting capabilities), folded in here with thanks to Konstantin Mirin. The sync_creatives assign operation opens too. Its operation const keeps the branches apart, so it doesn't need fix(schemas): open the capability blocks and containers 3.3 extends, against DR-0019 (#8501) #8772's named exception. From fix(schemas): open the capability blocks and containers 3.3 extends, against DR-0019 (#8501) #8772, boolean demographics on the overlay schemas is also deprecated as the 3.2 shorthand for { "age": true }. Senders MUST send the object form, receivers MUST accept true, and only support with gender: true satisfies a gender requirement. 4.0 removes the boolean form.

    112 locations stay closed: most for a structural reason, and the commercial terms as a hold until 4.0.

    • oneOf forms told apart by key presence: a2ui/bound-value.json and the brand.json document forms.
    • Held closed until 4.0, as a hold rather than a structural reason: commercial-terms, product-purchase, change-term, change-term-constraints, sla-window, bidding-policy, and the canonical measurement terms, performance standard, reporting commitment, pricing option and budget allocation.
    • Join keys: metric qualifier objects and forecast dimensions.
    • canonical-installment-ref and the JWS response-payload envelope.
    • Privacy clamps: the TMP identity and context match requests, catalog-item-reference-not-found-error, the per-agent PERMISSION_DENIED and BILLING_NOT_PERMITTED_FOR_AGENT details, the get_principal recognized, unconfigured and failed results and the sync_principal failed result, and the error objects of the get_reporting_status lookup_unavailable failure.
    • Credential-free reporting destinations. proposal-budget-constraint, the strict peer of budget-range, is held until 4.0 with the commercial terms.
    • No key material or markup: trust.json, on the signature-verification fetch path, and the declarative placement-presentation frame.
    • Maps keyed by identifiers (patternProperties).

    Where closure also rejected a specific field the protocol defines elsewhere, the opened schema names it in not: { anyOf: [{ required: [...] }] }, as fix(schemas): reopen the 3.2 proposal-flow schemas closed against DR-0019 #8531 did for canonical-product. For example, trackers and landing_page_url stay assign-only, hold entries carry no expires_at, and delivery-ready webhooks carry no access token. Each node with a named rejection says in its description what it rejects and why, since generated types can't express not.

    The additive-minor check now flags an added property only where the schema stays closed. It still fails on removals, renames, retypes, removed enum values, tightened bounds, new required names, and closing an open schema. The closed-anywhere-in-the-major rule and the reopening corrections are gone, and the baseline keeps 4 entries, each with its resolution.

    Generated types change. A generator that reads additionalProperties now treats the opened objects as open: json-schema-to-typescript gives them an index signature, and Pydantic models stop forbidding extra fields. A strict validator built from the 3.2 schemas still rejects 3.3 fields on these objects, so send a 3.3 field only to a 3.3 peer. The next 3.2.x patch (fix(schemas): open schemas that were closed by accident (3.2.x backport) #8864) opens the same locations that 3.2 has, all but one: it keeps get-reporting-status-response.json#/oneOf/1/oneOf/0 closed, as 3.2 published it.

  • 39334ab: spec(reporting): report definitions at contract_version 1.2 require a package_id dimension on media-buy reporting (experimental, Reliable Reporting: report-definition contract_version 1.2 requires a package_id dimension for media buys #8971).

    Reliable Reporting (media_buy.reporting_delivery, experimental) adds report-definition contract_version 1.2 in core/reporting-report-definition.json. A 1.2 definition keeps every 1.1 rule, including restatement_policy.official_correction_mode. When its dimensions include media_buy_id, they MUST also include package_id, so every row carries the buyer-visible package. A definition without media_buy_id, whose rows aggregate across media buys (an account-level summary, for example), is exempt at every version. Definitions at 1.0 and 1.1 keep validating unchanged; a grader SHOULD report one that includes media_buy_id but not package_id as an advisory finding.

    The version is declared in the definition and pinned by the offering's report_definition_uri and SHA-256, as for 1.1, so no capability or request field changes. Callers pinned below 3.3 accept only 1.0 and 1.1, so a seller MUST serve them offerings whose definitions are 1.0 or 1.1; a strict validator built from 3.2 rejects a 1.2 definition, which is acceptable for an experimental surface. At 1.2, media-buy-scoped rows MUST name the dimension media_buy_id, and the offering's reporting_profile.primary_keys MUST include package_id. The dimension is named package_id, matching media_buy_id; reporting subscription selectors and standard_dimensions keep calling the breakdown package (enums/reporting-dimension.json).

    New compliance vectors in test-vectors/reporting-report-definition/ include a 1.2 fixture with ["date", "media_buy_id", "package_id"] and a negative vector for a 1.2 media-buy definition without package_id. The reporting-reconciliation reference fixture and its digests are unchanged at 1.1.

  • b4284b7: spec(reporting): https_put file transfer and no buyer secrets for reporting delivery (experimental, Reliable Reporting: HTTPS push to a buyer endpoint authenticates as the seller and never holds a buyer secret; row push is reporting_webhook, object push is file_transfer #8149).

    Reliable Reporting managed delivery (media_buy.reporting_delivery, experimental):

    • No buyer secrets. For every managed pattern the seller authenticates as itself, through its advertised producer_identity. A seller MUST NOT hold, request, or store a caller-issued secret of any kind (password, API key, bearer token, OAuth client secret, private key, signed URL, or shared signing key), directly or through a processor acting for it, and a seller that does is non-conformant. The deprecated reporting_webhook.authentication block is not precedent. Stated in core/reporting-write-destination.json, core/agent-reporting-destination.json, core/reporting-delivery-method.json, get_reporting_status, and sync_principal.
    • Row push is reporting_webhook. Rows in an HTTP request body are the Core reporting_webhook transport, never file_transfer: it has no destination, manifest, materialization, or receipt.
    • https_put (experimental in 3.3). A new open file_transfer transport token for writing immutable objects and a manifest to a buyer HTTPS endpoint. It is conformant only when the manifest is written last, every request is signed by the seller under the Web Bot Auth profile with keys from its origin's key directory, and the endpoint passes a signed probe before ready. The probe carries the seller-issued destination_ref, and the endpoint echoes its nonce only after recognizing that reference. A write-only endpoint is allowed, with the signed probe in place of the read-back (proof_file_transfer, enums/reporting-destination-setup-state.json). producer_identity for https_put names the seller agent's signing origin. transport is already an open string, so no enum or shape changes.
  • a2a7d20: State what accepting signed commercial terms means. terms_digest covers the entire commercial_terms JSON value: every member at every depth, including ext and members a party does not recognize. Several schemas inside commercial_terms are already open, so the signed bytes can carry members a party's release does not define.

    • Accepting the terms binds the accepting party to every member. A party that cannot interpret every member MUST NOT accept them: a buyer declines with the new decline_proposals reason unrecognized_terms, a seller rejects the request that carries them (such as buy_products purchases) with the new error code UNRECOGNIZED_TERMS (the decline reason names the same condition from the buyer's side), and a governance agent denies the check. A member whose schema defines it as opaque, such as context, is interpreted by that definition.
    • A party computes or verifies terms_digest over the JSON value as received, never over a re-serialized parsed model, which can drop members the model does not declare.

    The rule is stated in media-buy/commercial-terms.json, the terms_digest description in core/canonical-proposal.json, governance/check-governance-request.json, and the proposal negotiation, buy_products, decline_proposals, and check_governance pages. The release notes, What's new in 3.3, and the 3.2 to 3.3 migration guide now state the acceptance rule after the note that commercial-terms is held closed until 4.0. No schema is opened or closed.

    The new storyboard media_buy_seller/unrecognized_terms_rejected first proves a plain buy_products purchase is accepted, then sends the identical purchase with adcp_compliance_undefined_member in format_option_refs[0] and expects UNRECOGNIZED_TERMS. That member name is reserved as undefined, so no conformant seller can interpret it.

  • 38a83d1: Add media_buy.supported_delivery_types to get_adcp_capabilities. A seller declares whether it sells guaranteed inventory, non_guaranteed inventory, or both, mirroring supported_pricing_models, so buyers can filter sellers before calling get_products. Like every capability declaration, it is a commitment: a declaring seller returns only products with a listed delivery_type. When absent, buyers treat the seller's delivery types as unknown.

  • 3bd51b8: State that a seller accepts a creative that conforms to the format option it targets (adcp#8918).

    • sync_creatives gains a "Format conformance" rule. A seller MUST NOT refuse, with a conformance code (CREATIVE_SIZE_MISMATCH, CREATIVE_VALUE_NOT_ALLOWED, CREATIVE_VALIDATION_FAILED_GENERIC, or VALIDATION_ERROR / INVALID_REQUEST against the assets), a creative on the grounds of a declared parameter that the creative satisfies, and MUST NOT enforce a narrower value than the one declared.
    • A closed set narrows a slot only when declared. With no cta_values, the cta slot takes free text and CREATIVE_VALUE_NOT_ALLOWED does not apply.
    • Any other narrowing parameter the option omits sets no limit through that parameter. Under technical_requirements_complete: true the seller holds no undeclared limit either, so a creative that conforms to every parameter is accepted. Without that assertion the omitted constraint stays undeclared, as before.
    • Refusals outside format conformance are unchanged: CREATIVE_REJECTED for content, brand-safety and accessibility review, POLICY_VIOLATION for seller advertising policy, and validation codes for corrupt or unfetchable assets.
    • The CREATIVE_VALUE_NOT_ALLOWED description and the cta_values descriptions on the native_in_feed and image canonicals now say the same. The canonical-formats and creative-formats docs carry the rule beside technical completeness.
    • New compliance scenario media_buy_seller/declared_format_option_acceptance (3.3, required by media_buy_seller, gated on creative.has_creative_library). It seeds a native_in_feed option that declares a 336x280 main_image, a 90-character title limit, no cta_values and technical_requirements_complete: true, then expects sync_creatives to accept a creative built exactly to it, with a free-text CTA and no icon.

    This tightens a seller obligation in the 3.3 beta. A seller that refused declared sizes or enforced an undeclared CTA list was already contradicting its own declaration; it now fails the new scenario.

  • 63d996b: Require experimental TMP Context Match caches in AdCP 3.3 to partition by
    trusted evaluation namespace as well as request hash, re-authorize warm hits,
    and bypass caching when the required context cannot be established. Keep
    provider model-deployment changes under the existing cache_ttl policy, state
    the stale-entry window, and recommend lowering TTL before such deployments.
    The 3.1.22 emergency privacy and request-partitioning corrections remain in
    force; no published 3.1 or 3.2 release artifact changes.

  • 7ce107a: Add 3gp, mpeg, and m4v to the containers enum of the video asset requirements (core/requirements/video-asset-requirements.json), so a seller that accepts those files can declare them. Three additive enum values: no existing value changes, and clients already tolerate unknown enum values. Proposed for 3.3 by consent (adcp#8107).

  • 3deb1cf: Keep 3.3 additions off the deprecated create_media_buy and update_media_buy tasks (adcp#8501). Both are compatibility tasks that buyers are moving off, so 3.3 adds nothing to them: a field that exists only there is one more gap for every migration. Six fields that the 3.3 betas added to them are removed from them. Where a live task (buy_products, accept_proposal, control_media_buy, get_media_buys, sync_creatives assignment_operations) has the same field, it stays there unchanged.

    This is a beta-to-beta change. No stable release carried these fields. The betas are immutable, so a buyer, seller, or SDK built from a beta bundle has them to remove. The schemas are open, so a seller on the later schema ignores them like any unknown field rather than rejecting the request.

    • predecessor_media_buy_id and lineage_reason (experimental media_buy.lineage, feat(media-buy): forward-only lineage for renewal and replacement buys #8038, from 3.3.0-beta.0). Removed from the create_media_buy request, with their paired dependencies. They stay on the buy_products and accept_proposal requests, on get_media_buys readback and its predecessor_media_buy_id filter, and on core/media-buy.json.
    • artifact_webhook.signing_profile (experimental, docs(security): add the Web Bot Auth request-signing profile #7894, from 3.3.0-beta.0). Removed from the create_media_buy request, with its rule against sending it next to authentication. No live task has artifact_webhook, so it lives nowhere: an artifact_webhook without authentication is signed with adcp/webhook-signing/v1. signing_profile stays on push_notification_config, reporting_webhook, and the notification configurations, and webhook_signing.profiles no longer lists artifact_webhook.
    • start_requires_all_creatives_approved (feat(media-buy): define creative approval startup policy #8485, from 3.3.0-beta.1). Removed from media-buy/package-request.json (create_media_buy packages and update_media_buy new_packages), media-buy/package-update.json, and core/package.json (the package readback in their responses). It stays on control_media_buy package controls (media-buy/package-control.json), get_media_buys package readback, the update_creative_start_policy available action, and media_buy.features.creative_start_policy, whose description now names only control_media_buy.
    • target_audiences[] (experimental media_buy.audience_evidence_targets, feat(media-buy): experimental target_audiences in audience_evidence_requirements #8215, from 3.3.0-beta.1). Removed from media-buy/package-request.json, with its dependencies entry. With the get_products filters copy withdrawn in the same release, no 3.3 wire form remains: sellers stop listing the feature id, and core/audience-evidence-target.json and enums/audience-evidence-relationship.json are removed, along with their index.json registrations and tests/audience-evidence-targets.test.cjs. The stable inline relationship enums on audience evidence are unchanged. The design and its matching rules are kept under the 4.0 check purchase_target_audiences_required_in_4_0, whose detection no longer depends on the retired feature id.
    • trackers and landing_page_url on package creative assignments (feat(creative): add assignment-scoped measurement trackers #8220, feat(creative): support assignment landing page overrides #8180, from 3.3.0-beta.0). Removed from core/creative-assignment.json, which only create_media_buy and update_media_buy requests and their package readback use. They stay on sync_creatives assignment_operations assign, read back on list_creatives and get_media_buys, which defines its own assignment rows. creative.supports_assignment_trackers and creative.supports_assignment_landing_page now name only sync_creatives.
    • billing_measurement.counting_mechanisms[] (experimental media_buy.measurement_provenance, feat(schema): experimental collection-mechanism vocabulary for counting_mechanisms and measurement_provenance #7940, from 3.3.0-beta.2). Removed from core/measurement-terms.json, which only get_products products and create_media_buy and update_media_buy packages use, so this covers all three tasks. It lives nowhere in 3.3; the canonical commercial terms, held closed until 4.0, gain it then (canonical_counting_mechanisms_required_in_4_0, whose design notes now record it). vendor_metric_provenance[] and enums/collection-mechanism.json stay.

    expected_confirmation_at stays on every submitted response, create_media_buy included. The training agent stops echoing the start gate on create_media_buy and update_media_buy packages. It ignores assignment trackers and landing_page_url on their creative assignments and does not echo assign-set ones in their responses. get_media_buys still reads back what sync_creatives assign set. The 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, and the 3.3 beta page list the removals under "Withdrawn from the deprecated tasks".

  • 18da1a4: Withdraw the 3.3 additions to the deprecated get_products task and the deprecated sync_creatives assignments[] row, and move execution readiness to list_products (adcp#8501, entries 20–25 and the get_products rows of the deprecated-task table). 3.3 adds no field that exists only on a deprecated task. Where a live task lacks the capability, it moves there or waits for 4.0.

    All of these shipped in 3.3 betas and are removed after 3.3.0-beta.5. This is a beta-to-beta change, not a change to a stable release. The betas are immutable, so a seller or SDK built from a beta bundle has the surfaces below to remove.

    Exact-package forecasts on get_products (feat(media-buy): forecast exact packages before booking #8468, beta.1 to beta.5). Removed: refine[].package, media-buy/package-forecast-input.json, the request rule tying package to buying_mode: "refine" and to non-finalize entries, and refinement_applied[] result_product_id, resolved_start_time and resolved_end_time with their applied rule. refinement_applied is optional again for every request. The forecast has no 3.3 home; where it belongs on the compact lifecycle is an open working-group question.

    get_products filters.target_audiences (feat(media-buy): experimental target_audiences in audience_evidence_requirements #8215, experimental, beta.1 to beta.5). Removed from core/product-filters.json, with its dependencies entry. It is planned for list_products offer_filters and buy_products purchases in 4.0 (purchase_target_audiences_required_in_4_0).

    Collection cards on get_products (feat(schema): experimental collection objects in product and proposal responses #8141, experimental, beta.0 to beta.5). Removed: the include_collections request flag, the response-level collections array and its dependencies entry, the collections branch of get-products-rejected.json, and include_collections in the wholesale_feed_version scope. list_products, request_proposals and refine_proposals keep both.

    Execution readiness (feat(schema): add experimental per-account execution readiness #7934, experimental, beta.1 to beta.5) moves to list_products. include_execution_readiness leaves the get_products request and the execution_readiness map leaves its response. Both are added to the open list_products request and response, with the same shape and rules; the map is versioned independently of feed_version and is absent on an unchanged outcome. The media_buy.execution_readiness storyboard now drives list_products. binding_field now names the buy_products paths, purchases[].optimization_goals[].event_sources[].event_source_id and purchases[].catalog_ids[], instead of the legacy create_media_buy packages[] paths, and execution_requirements documents the purchase binding beside the legacy one.

    price_adjustments on get_products pricing options (feat(schema): selection-dependent price_adjustments on fixed-price pricing options #7955, experimental, beta.1 to beta.5). Removed from the cpm, vcpm, cpc, cpcv, cpv, cpp and flat_rate options with their dependencies, along with pricing-options/price-adjustments.json, error-details/price-adjustments-mismatch.json, the product rule that a placement-selection row requires overlay_support.placement_selection, the price_adjustments_resolution verifier constraint on product-purchase.json, and the price-adjustments test vectors. A seller stops listing media_buy.price_adjustments. The design is kept for the canonical pricing option in 4.0 (canonical_price_adjustments_required_in_4_0).

    sync_creatives assignments[] landing_page_url and trackers (feat(creative): support assignment landing page overrides #8180, feat(creative): add assignment-scoped measurement trackers #8220, beta.0 to beta.5). Removed from the deprecated row, which now rejects them by name. The assignment_operations assign operation keeps both.

    The consumed changesets for these PRs stay in .changeset/pre/ as history. The 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, and the 3.3 beta page say what to remove under "Withdrawn from the deprecated tasks".

Patch Changes

  • b195f57: Compliance storyboards now check that sellers never author operator_fee (adcp#8367). media_buy_seller/product_filter_behavior checks get_products pricing_options[].eligible_adjustments[] and pricing_options[].price_breakdown.adjustments[].kind. media_buy_seller/total_budget_redistribution checks create_media_buy packages[].price_breakdown.adjustments[].kind and update_media_buy affected_packages[].price_breakdown.adjustments[].kind. The checks pass when a seller returns no breakdown or eligible_adjustments. They are advisory until runner capability version 17.0.0 and then become required. total_budget_redistribution now declares requires: field_excludes_runner, which the storyboard schema mandates for field_excludes.

  • c951012: Docs: DR-0036 records the decision of the 2026-11-09 working-group session. Schemas are open within a major. A schema is closed only for a structural reason: oneOf branch disjointness, a closed key set or vocabulary, or a signed or binding payload. Opening a 3.x schema that was closed without such a reason is a correction, so 3.3 opens those schemas and a 3.2.x patch does too. Once opened, a schema takes additions in later minors. The versioning page no longer says closed schemas stay closed until the next major. DR-0019 is superseded. DR-0032 and DR-0033, proposed in docs(governance): DR-0032 and DR-0033, revised against DR-0036 #8519 and never ratified, are recorded as withdrawn in favor of the versioning rules. No schema changes.

    Docs: a deprecation needs no minimum notice period before its removal in the next major. A deprecated feature is never removed within the major that deprecated it. The next major may remove it with no minimum notice, because removals are what a major is for. The previous major's support window of at least 12 months after the successor's GA protects implementers. The 6-month deprecation notice is gone from the versioning page, the cadence table, the specification lifecycle, and the pages that cited it. Experimental surfaces keep their 6-week notice within a major. Brian O'Kelley ruled this on 2026-11-10, and it is open for working-group comment on RFC RFC: AdCP 4.0 — a fast, cleanup-first major (scope, principles, schedule) #8756 until 2026-12-04.

  • 5541479: Stop the dependency_impairment and dependency_impairment_cardinality storyboards from failing sellers whose selected format option is not an image format (adcp#8770). Both storyboards send a fixed 300x250 image creative against the first product's first format option. When that option is a display_tag, video_vast or other non-image kind, the creative phases are now skipped instead of failing a seller that correctly refuses an image it does not accept. Image sellers run the storyboards unchanged.

  • e212baa: Campaign governance errata: make the task pages, audit-trail, safety-model and overview pages agree with the specification and schemas (adcp#8733, PR 1 of 3). No wire field, enum member or schema validation outcome changes.

    • Governance mode is described as governance agent configuration, not a plan field set through sync_plans. An agent that reports mode records the mode in force on each check entry.
    • The safety model no longer promises budget reservation. Budget checks are point-in-time, as the specification already says. Where the pages said an intent or governance "reserves" an amount, they now say the ledger commits it when the outcome is reported.
    • The get_plan_audit_logs field table names plans[].entries[].verdict instead of status, and the delivery outcome example is buyer-called.
    • A plan re-sync is no longer described as re-evaluating active campaigns. Active buys are evaluated against the updated plan on their next check_governance call.
    • Drift metrics use the schema vocabulary throughout: escalations[], escalation_rate, escalation_rate_trend, thresholds.escalation_rate_min and escalation_rate_max. The human_review_rate* and human_reviews[] names never existed in a schema.
    • Geo findings in the examples use geo_compliance, matching categories_evaluated on the same page.
    • The legacy check_governance response branch (responses without check_type) is described as the legacy compatibility shape accepted during 3.x migration.
    • The trailing-window aggregation key changes from (buyer_agent, seller_agent, account_id) to (owner_principal, seller_agent) in the specification and in the governance.aggregation_window_days capability description. owner_principal is a defined term for the authenticated buyer principal that synchronized the plan. No governance schema has carried an account_id field; a governance agent that derived an account from the plan and partitioned its aggregate by it now aggregates across that principal's plans per seller.
  • 3bb0710: Build legacy inline creative manifests from the captured format's exact required slots, preserving the legacy wire and preflighting both manifests before any purchase.

  • eede511: Loosen seventeen over-specified URL patterns to ^https:// (adcp#8398). Nine attestation URLs (core/attestation-capabilities.json, attestation-evaluation.json, attestation-issuer.json, attestation-reference.json, attestation-subject.json, product-audience-evidence-requirements.json) dropped a pattern that refused userinfo and fragments. Eight reporting URIs (core/reporting-canonical-content-digest.json, reporting-delivery-capabilities.json, reporting-delivery-offering.json, reporting-reliability-statistics.json, reporting-revision.json) dropped a lexical private-address denylist that could not see DNS or redirects. Every value the old patterns accepted still validates. The fetch-time SSRF rules (the attestation fetch contract and safe_schema_fetch) are unchanged, and the descriptions no longer claim the schema enforces them. The origin-shaped patterns, governance/accepted-governance-agents.json, and reference-renderer.source_repository are unchanged.

  • 8cda67a: In three storyboards, a skipped optional tool no longer causes the stateful steps after it to fail.

    • provenance_audit_observation (1.1.0): both audit-observation reads declare sync_creatives, the tool whose state they read, and each runs in its own phase after the sync. Sellers without sync_creatives skip the sync and both reads instead of failing them, and their verifier discovery is still graded.
    • create_media_buy_async_lifecycle (1.1.0): each optional get_task_status and list_tasks read runs in its own phase, after the submit or completion phase it depends on. The completed-task reads keep the force_task_completion gate. A missing read no longer blocks the other read or the controller completion.
    • governance_agent_binding_acceptance (1.1.0): the optional comply_test_controller read and the recovery sync_governance each run in their own phase after account setup. Sellers without the controller still have their recovery graded.
  • 8f159e4: Gate product_signal_targeting and cross_path_targeting_provenance on wholesale support in both media_buy.buying_modes and signals.discovery_modes. A seller that advertises only brief discovery no longer runs them. Their negative probes now cascade-skip when product discovery fails, instead of sending an unresolved $context.product_id.

  • 9395a3e: Docs: Python adcp 10.0.0b13 is on PyPI, adopting the signed 3.3.0-beta.5 bundle and negotiating only 3.3-beta.5. The 3.3 beta program page, the beta checkpoint table, and Choose your SDK now name it, with its install command and adcp-reporting-storage 0.2.0b3 for Reliable Reporting storage.

  • e64e858: Docs: refresh the 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, and the 3.3 beta program page through 3.3.0-beta.5. Adds beta.4 and beta.5 to the checkpoint and wire-pin tables, with curated sections. Beta.4 covers the reporting-subscription coverage fixes and probe reset, replace that transfers assignment settings, tracker-slot limits, BUDGET_TOO_LOW details, creative.supports_provenance, opportunity on explicit-package buys, undefined-property reporting, and the new storyboards. Beta.5 covers match keys, the stable sales-fixed-rate specialism, and the bundled Public Suffix List. The SDK guidance now records that @adcp/sdk 17.0.0-beta.18 and later and Python adcp 10.0.0b12 support beta.4, and the in-review tables reflect the 3.3.0 milestone as of 2026-11-08.

  • 8558eef: Stop signed functional storyboard requests from exhausting the per-keyid cap that the signed-requests rate_abuse vector grades (adcp#8877). Functional dispatch in test-kits/signed-requests-runner.yaml signed with test-ed25519-2026, the same keyid vector 020-rate-abuse caps at 100 for the test counterparty, so a full compliance run could hit the cap before the signed-requests vectors started and fail them with request_signature_rate_abuse. Functional dispatch now signs with a dedicated test-functional-2026 Ed25519 key that no conformance vector uses, published in the request-signing keys.json and declared in runner_signing_keys. The rate_abuse block now states that agents MAY lower the per-keyid cap to the grading target for the vector 020 keyid (test-ed25519-2026) only, and MUST NOT apply the lowered cap to the functional-dispatch keyid. Sellers that register the runner signing keys individually rather than loading the published keys.json must add test-functional-2026 to their test counterparty. Sellers that configure one global per-keyid cap on their replay store (as the SDK reference stores take, e.g. maxEntriesPerKeyid: 100) must scope the lowered cap to test-ed25519-2026, for example with a keyid-aware wrapper, or functional storyboards hit the cap on test-functional-2026 instead.

  • 9db8225: Docs: the public test agent's opt-in 3.3 preview moves to 3.3-beta.4, the beta that @adcp/sdk 17.0.0-beta.18 and later negotiate. The 3.3 beta program page and the quickstart name the new pin, and the page notes that 3.3.0-beta.5 is published but no SDK negotiates it yet. The preview now follows the beta the current SDK prerelease negotiates rather than the latest published beta. The beta tracker records that supported match keys merged in feat(media-buy): declare supported match keys for cross-publisher frequency capping #8446.

  • 4942cab: Docs: the public test agent's opt-in 3.3 preview moves to 3.3-beta.5, the beta that @adcp/sdk 17.0.0-beta.21 and later negotiate. The 3.3 beta program page and the quickstart name the new pin. The SDK guidance and the beta checkpoint table record that @adcp/sdk 17.0.0-beta.21 and later bundle 3.3.0-beta.5, and that 17.0.0-beta.18 through 17.0.0-beta.20 bundle beta.4. Python adoption of beta.5 is in flight.

  • fc3c5bd: Docs: state the rules for what changes between releases at the top of the versioning page. A minor only adds, a replaced field is emitted alongside its replacement until the next major, and removals and breaking changes happen in a major. A fourth rule keeps a field off a mutating request in a minor when an older seller that ignores it would commit to something different, unless the field ships behind a capability the seller declares. Removes text from that page that told SDKs what to do or described translating between versions, and corrects one sentence in the create_media_buy reference that said new keys could join a closed schema in a minor. Wire behavior is unchanged.

  • 7ec4059: Stop the webhook_emission storyboard from failing sellers whose create_media_buy completes synchronously. When the primary trigger returns the media buy inline, the storyboard now checks that no task webhook arrives for it and skips the emitted-webhook phases. It still grades the webhook-signing JWKS of a synchronous seller that declares webhook_signing.supported: true. Triggers that return submitted, or working without a media_buy_id, are still graded on signed webhook delivery. A working response that carries media_buy_id is classified as synchronous, and its completion webhook fails synchronous_trigger_silence, until the runner reads the task status (Storyboard runner: create_media_buy context extractor records media_buy_id from interim task envelopes adcp-client#3682).

  • 50fafb3: Stop product_coverage_filters and portfolio_routing_scope from failing sellers that declare only brief/refine buying modes. The get_products coverage phase of product_coverage_filters now requires wholesale in media_buy.buying_modes, and its list_products phase runs independently. In portfolio_routing_scope, the wholesale read that checks returned channels against the declared allowlist moves to its own phase, which runs only for sellers that declare wholesale, so brief-only sellers are no longer sent a wholesale request they cannot serve.

@mintlify

mintlify Bot commented Nov 8, 2026 •

Copy link
Copy Markdown

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

Project Status Preview Updated
adcp 🟢 Ready View Preview Nov 13, 2026, 7:29 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: 9db8225
Prior ref: b7fed8b
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42441664058
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: e64e858
Prior ref: 3737b94
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42445356717
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: 4942cab
Prior ref: 74a2802
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42483325870
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: 9395a3e
Prior ref: 9329204
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42490862681
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: 2877ec0
Prior ref: ff9a8a8
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42504731987
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 ff9a8a8 to 12660a9 Compare November 8, 2026 17:30
bokelley added a commit that referenced this pull request Nov 8, 2026
… snapshots from the Fly image (#8814)

The 3.3.0-beta.6 Version Packages PR (#8801) fails both production
Docker builds: /app measures 7,524 MiB against the 7,424 MiB budget.
The growth is the release itself. Its schema bundle is 144 MiB, and
every file carries a versioned $id, so it cannot be hard-linked to
beta.5. Compliance adds 10 MiB and the archive 27 MiB. Main was already
within about 1 MiB of the budget locally, so the next release had
nowhere to go.

Two runtime retention fixes, with the budget unchanged:

- Protocol tarballs were 934 MiB of the image. #8752 offloaded CDN-verified
  archives only outside the required schema closure, but archive bodies
  have no runtime reader besides the /protocol download route, which
  already redirects offloaded archives to the R2 CDN. Offload every
  versioned archive that R2 discovery lists and whose bytes match. A
  required release's archive that R2 does not list yet, such as the
  release a Version Packages build is cutting, stays local; any other
  missing archive still fails the build. latest.tgz, sidecars and the
  discovery inventory stay local.
- update-release-docs-nav only ever added dist/docs allowlist rules, so
  superseded snapshots (3.1.31, 3.3.0-beta.3, 3.3.0-beta.4) were still
  copied into the image. Regenerate the allowlist from docs.json on every
  release and add a test that fails when the committed .dockerignore
  drifts from navigation.

Released artifacts in Git and on the CDN are unchanged.

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: fafe043
Prior ref: 12660a9
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42520030584
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: 867fdce
Prior ref: fa0f9a2
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42621216683
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: fc3c5bd
Prior ref: 2f0d61f
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42656743599
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: fad5b30
Prior ref: e8c5e18
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/42668998382
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: 38a83d1
Prior ref: ec353ee
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43451047995
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: a7af517
Prior ref: 332563b
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43460723174
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: e903ee6
Prior ref: 5f89159
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43470971831
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: 72f34ec
Prior ref: 250dab0
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43476221640
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: 39334ab
Prior ref: 025abe3
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43482298186
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 025abe3 to 2ff85b3 Compare November 13, 2026 18:31
@bokelley
bokelley marked this pull request as ready for review November 13, 2026 18:33
@aao-secretariat

Copy link
Copy Markdown
Contributor

Ladon does not review bot-authored PRs.

@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: aa94f36
Prior ref: 2ff85b3
Candidate: not pushed
Observed ref: absent/unknown
Workflow: https://github.com/adcontextprotocol/adcp/actions/runs/43486480530
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 2ff85b3 to 7b94129 Compare November 13, 2026 18:58
@bokelley
bokelley marked this pull request as ready for review November 13, 2026 18:59

@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-beta.6 at exact head 7b94129 (base = main tip aa94f36; CI green, 70 checks). Rolling beta under the standing approval.

🤖 Generated with Claude Code

@bokelley
bokelley merged commit bf4aa6d into main Nov 13, 2026
70 checks passed
@bokelley
bokelley deleted the changeset-release/main branch November 13, 2026 19:41
bokelley added a commit that referenced this pull request Nov 13, 2026
3.3.0-beta.6 published on 2026-11-13 (tag v3.3.0-beta.6 at bf4aa6d,
from Version Packages #8801). The pages already give that date, so drop
the four markers that held it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
3.3.0-beta.6 published on 2026-11-13 (tag v3.3.0-beta.6 at bf4aa6d,
from Version Packages #8801). The pages already give that date, so drop
the four markers that held it.

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

This branch was successfully deployed

1 active deployment
staging — 7b941292 Deployed Nov 13, 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