Version Packages#5909
Merged
Merged
Conversation
![aao-secretariat[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
There was a problem hiding this comment.
Argus is not auto-reviewing this PR because it is a generated Changesets release PR.
A human release reviewer should verify CI, package/version/changelog changes, and generated dist/** artifacts. Argus will resume on source PRs before the next release PR is generated.
bokelley
added a commit
that referenced
this pull request
Jul 19, 2026
* fix(delivery-metrics): allow null for video-only metrics (quartile_data, completion_rate) (#5837) * fix(delivery-metrics): allow null for video-only metrics (quartile_data, completion_rate) Sellers running non-video inventory (display, audio-only, DOOH-without-video) legitimately return null for video-only metrics — the correct "not applicable" signal. The schema required type:"number"/"object" and rejected null, so receivers throw a validation error on every valid display-inventory delivery report. - delivery-metrics.json: completion_rate -> ["number","null"], quartile_data -> ["object","null"] (min/max on completion_rate still apply to non-null). - get-media-buy-delivery-response.json: aggregated_totals.completion_rate gets the same loosening so the aggregate path can't re-trigger the failure. - Docs: scope the null convention to these two fields; omission remains the canonical "not applicable" signal for every other metric. Refs Sentry AGENTIC-API-9P (87 events/5 days; PubX, BidMachine, Ozone, Vox). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(docs): escape bare < in spec-guardian so Mintlify link check parses it 'overturn <5%' parsed as a JSX tag open (< before a digit), failing the Mintlify broken-links check that runs on any docs change. Escape to <5%. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> # Conflicts: # specs/spec-guardian.md * chore(ci): add 3.1.x to release and CI workflow branch filters Enables the Release workflow, Build Check, Changeset Check, and CodeQL to fire on pushes and PRs targeting the 3.1.x maintenance branch. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(storyboards): port governance approval and stale date fixes to 3.1.x Cherry-picks two patch fixes from main needed for storyboard coverage to pass on 3.1.x: - Fix brand-handlers to always return REFERENCE_NOT_FOUND (removing 3.0 compat path that returned BRAND_NOT_FOUND), fixing brand_baseline failure - Move stale exclusivity/rights window dates in brand-handlers from 2026-2027 to 2099 to prevent date-expiry storyboard failures - Fix governance compliance storyboards for human approval and signal activation enforcement Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(signals): port signal governance enforcement fix to 3.1.x Cherry-picks a335070 from main: signal agents now fail closed on governed accounts without a valid approval context, and governance compliance checks no longer require the signals tenant to own sync_plans. Fixes the activate_signal_denied storyboard floor failure on 3.1.x. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore(deps): bump @adcp/sdk to 9.6.2 on 3.1.x The signal governance enforcement fix cherry-picked in da636b4 was validated on main under @adcp/sdk 9.6.2 (bumped there in 7a27263 the day before the fix landed). Under 9.3.0 the storyboard runner skips sync_accounts as not_applicable when require_operator_auth is true, so the governance_denied storyboard never registers a governance agent and activate_signal returns success instead of PERMISSION_DENIED, leaving the signals 3.0-compat leg at 64 clean vs the 65 floor. Verified locally: 3.0-compat matrix passes all tenants (signals 65 clean, 108 steps, matching main) and current matrix passes (signals 113 clean, 137 steps). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(deps): regenerate lockfile with npm 10 for CI compatibility The previous lockfile was regenerated by a locally wrapped npm 11 that pruned nested proxy-agent@8.0.2 entries, so npm ci on CI (node 22, npm 10) failed with a lock sync error. Restore the prior lockfile and apply only the @adcp/sdk 9.6.2 bump via npm 10, matching CI. Verified with npm@10 ci --dry-run plus a rerun of typecheck and the 3.0-compat storyboard matrix (all tenants meet floors). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Version Packages (#5842) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(training-agent): backport publisher_domain filter to 3.1.x (#5868) * feat(training-agent): add publisher_domain filter to get_products (#5867) * feat(discovery): add publisher_domain filter to get_products Adds a publisher_domain filter to product-filters.json so buyers can discover which products from a seller cover a given publisher domain. A product matches when at least one publisher_properties entry targets the specified domain exactly. Implements the training-agent filter alongside schema and tests. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat(training-agent): add publisher_domain filter to get_products Adds publisher_domain as a filter on get_products so buyers can narrow results to products whose publisher_properties cover a specific domain. - Adds publisher_domain to the source schema (static/schemas/source) so it survives schema rebuilds - Handles both publisher_domain (singular) and publisher_domains[] (plural array) forms of PublisherPropertySelector, matching the logic in adagents-manager.ts - Canonicalizes the filter value and stored values via canonicalizePublisherDomain so BBC.com / bbc.com/ / bbc.com all match - Adds typeof guard to reject non-string values passed as the filter Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(ci): revert immutable dist artifact edit The dist/schemas/3.1.0/ artifacts are released and immutable. The publisher_domain field belongs in the source schema only; the versioned dist is generated by npm run version when the changeset is processed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * chore(changeset): downgrade to patch for 3.1.x backport --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> * Version Packages (#5869) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(protocol): restore the supported 3.1 contract (#5908) * Version Packages (#5909) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: Rachit <43431004+rachitm022@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Nastassia Fulconis <nfulconis@scope3.com> Co-authored-by: aao-release-bot[bot] <280565558+aao-release-bot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Nastassia Fulconis <nastassia.fulconis@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to 3.1.x, this PR will be updated.
Releases
adcontextprotocol@3.1.4
Patch Changes
get_products.filters.publisher_domainfield and its incorrect plural-selector implementation. Exact 3.1.3 artifacts remain available as an immutable withdrawn release record.