Skip to content

Version Packages - #8886

Merged
bokelley merged 1 commit into
3.2.xfrom
changeset-release/3.2.x
Nov 10, 2026
Merged

bokelley merged 1 commit into
3.2.xfrom
changeset-release/3.2.x

Conversation

@aao-release-bot

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 3.2.x, this PR will be updated.

Releases

adcontextprotocol@3.2.10

Patch Changes

  • bdc61ec: Stop the 3.2 collection and reporting storyboards from failing sellers on features they do not offer. Backports the applicability part of fix(compliance): qualify independent catalog reporting scopes #8336 and narrows fix(compliance): qualify independent catalog collection features #8428 for the 3.2 runner (3.2.x: backport #8428 / #8336 so collection and reporting storyboards stop failing sellers on seeded-only features #8744).

    advanced_delivery_reporting no longer seeds a video product. It discovers a native wholesale sandbox product that advertises format breakdown, with a fixed-price CPM option, and grades metric narrowing, the by_format array, truncation disclosure and the applied-sort echo on that product. When no product qualifies, the storyboard reports fixture_unsatisfied: the feature was not tested, which is neither a pass nor proof of nonsupport. It no longer grades time_based_views, because the controller cannot inject view observations and the old checks expected an invented 2-second threshold.

    collection_selection and owner_sold_channel_carriage keep their existing checks. They now run only when wholesale discovery finds a native product that allows collection targeting and declares at least one domain-qualified collection. Otherwise they report fixture_unsatisfied. Discovery failures still fail. Sellers that do not advertise the wholesale buying mode grade all three storyboards not applicable.

    Full independent collection grading needs the 3.3 fixture contract and runner, and ships in 3.3. No schema changes.

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

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

@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 the 3.2.10 release artifacts on final head af2f7a5. Verified: generated by release.yml (push run 42621225452, attempt 2) on 3.2.x@5541479a3, which is the current branch head and this PR's base. The changelog lists only adcontextprotocol@3.2.10 patch changes (bdc61ec #8826, 5541479 #8847, 8f159e4 #8839). The version agrees across package.json, CHANGELOG and dist/protocol/3.2.10.tgz{,.sha256,.sig,.crt}. The other changes are the consumed changesets and release metadata. CI: 44 pass, 6 skipped.

@bokelley
bokelley marked this pull request as ready for review November 10, 2026 13:19
@bokelley
bokelley merged commit a6163fb into 3.2.x Nov 10, 2026
51 checks passed
@bokelley
bokelley deleted the changeset-release/3.2.x branch November 10, 2026 13:19
@aao-secretariat

Copy link
Copy Markdown
Contributor

Ladon does not review bot-authored PRs.

aymeric45 pushed a commit to aymeric45/adcp that referenced this pull request Nov 11, 2026
Forward-merges the published 3.2.10 release (v3.2.10 = a6163fb, the
3.2.x head) and the three 3.2.x maintenance commits since v3.2.9: adcontextprotocol#8826,
adcontextprotocol#8839 and adcontextprotocol#8847, released by the adcontextprotocol#8886 Version Packages merge.

Release records:
- dist/compliance/3.2.10, dist/schemas/3.2.10 and the signed
  dist/protocol/3.2.10.tgz tuple are taken from v3.2.10 unchanged.
- dist/schemas/index.json and latest.json are regenerated
  (forward-merge-release-records.cjs schema-discovery).
- CHANGELOG.md is main's file plus the 3.2.10 block
  (forward-merge-release-records.cjs changelog).
- package.json, package-lock.json, static/schemas/source/index.json: main's.
- static/compliance/published-versions.json: main's. 3.2.x's only extra
  entry is 3.2.10, which is registered in a separate commit after
  qualification.

adcontextprotocol#8839 and adcontextprotocol#8847 are cherry-picks of main's adcontextprotocol#8838 and adcontextprotocol#8841. Their
storyboards and tests auto-merged to main's bytes; nothing changes.

Content conflicts, all from adcontextprotocol#8826 and all resolved to main's file. adcontextprotocol#8826 is
an SDK 14 narrowing of adcontextprotocol#8336 and adcontextprotocol#8428 for the 3.2 runner; main carries both
in full on SDK 17:
- advanced_delivery_reporting.yaml: main's adcontextprotocol#8336 storyboard, with the
  adcontextprotocol#8376 price snapshot and the separate time_based_delivery_reporting scope.
- collection_selection.yaml, owner_sold_channel_carriage.yaml: main's adcontextprotocol#8428
  independently qualified catalog scopes. The 3.2.x side's
  native_collection_product discovery gate is dropped.
- docs/reference/known-limitations.mdx: main's catalog reporting and
  collection bullets already state the scope and fixture_unsatisfied
  semantics the 3.2.x paragraph describes.
- tests/sdk-runner-capability-gates.test.cjs: main's reporting gate test
  (both reporting storyboards). The 3.2.x single-storyboard variant is
  dropped.

Auto-merge reverted: the non-conflicting adcontextprotocol#8826 collection gate test
("<name> grades only sellers whose catalog offers selectable collections")
asserts the 3.2-only native_collection_product handle, which main's
storyboards do not declare.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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