Version Packages (rc)

[ohalushchak-exadel]

Bumps the prerelease package from 3.1.0-rc.10 to 3.1.0-rc.11 and updates the schema registry version metadata.

Adds the generated 3.1.0-rc.11 schema, compliance, and protocol tarball artifacts, including the checksum sidecar. The cosign .sig/.crt sidecars are produced by the release workflow on merge (Sigstore OIDC bound to the workflow identity).

Rolls up the changesets merged since rc.10 — notably the required seller_agent_url on context_match_request (#5410), plus the matching identity_match_request field changeset and the other pending entries on main.

Why this was cut by hand

The release automation did not open this PR after #5410 merged: the Release workflow's has_release_artifacts check matched the already-committed rc.10 dist artifacts in main's tree (package.json is still 3.1.0-rc.10), so the changesets version-PR step was skipped and the run took the publish path instead. Same manual procedure as rc.10 (#5405): npm run version → commit → "Version Packages (rc)" PR → merge publishes.

Validation

npm run version succeeded (rc.11 schema/compliance/protocol artifacts generated). Schema-release tests pass locally: test:schemas (16), test:examples (42 — the now-required seller_agent_url is present in both context-match fixtures), test:json-schema (282), test:composed (107), test:dist-schema-version-ids. Full CI runs here.

Merging this tags + publishes v3.1.0-rc.11.

[aao-release-bot]

Mechanical rc.11 release rollup, internally consistent. Right shape for a Version Packages PR: source bump + generated dist artifacts, nothing hand-edited that the generator owns.

Things I checked

• Version strings agree across every surface, all rc.11: package.json:3, both package-lock.json root + packages."" entries, static/schemas/source/index.json (adcp_version and published_version), the new CHANGELOG.md ## 3.1.0-rc.11 section, and all 1037 added dist paths. Zero stale rc.10 paths introduced. Remaining lockfile churn is npm peer: true metadata only.
• .changeset/pre.json consumes exactly one new entry — tmp-context-match-seller-agent-url — matching the single rc.11 CHANGELOG Minor entry. tmp-identity-match-seller-agent-url was already consumed and correctly not re-listed, consistent with the PR body noting it landed earlier.
• CHANGELOG provenance: commit 563eaf4 resolves to "spec(tmp): add required seller_agent_url to context_match_request (#5410)."
• The only static/schemas/source/** touch is the two version strings in index.json — no field, type, enum, or required-list change. No wire-shape drift in this PR; the substantive seller_agent_url change was reviewed and merged upstream in #5410.
• Generated dist/schemas/3.1.0-rc.11/tmp/context-match-request.json carries seller_agent_url in required with the full description on the wire. The rollup actually emitted the rolled-up change.
• ad-tech-protocol-expert: sound. Minor categorization is correct, not spec drift — docs/reference/experimental-status.mdx:36 states verbatim that on x-status: experimental surfaces "Required fields may become optional and vice versa," and the 3.x optional→required deprecation gate (versioning.mdx:176) binds stable surfaces only. context_match_request is experimental at HEAD, so a new required field within a 3.x release is Minor, not Major.

Follow-ups (non-blocking — file as issues)

• The experimental-status policy attaches a 6-week breaking-change notice obligation (experimental-status.mdx:43) to tmp surfaces. That obligation lived with #5410, not this PR — but worth confirming the notice was logged. Does not affect the semver tier or this tag.

One dry note: the release automation skipped this because has_release_artifacts matched the rc.10 dist already sitting in main's tree while package.json stayed rc.10. Cutting it by hand is fine; the gate keying off committed artifacts instead of the declared version is the thing worth a follow-up.

Ship it once CI validates the schema-release suite.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
adcp	🔴 Failed	–	Jun 8, 2026, 12:36 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.