Skip to content

Version Packages (rc)#5217

Open
aao-release-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages (rc)#5217
aao-release-bot[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@aao-release-bot
Copy link
Copy Markdown
Contributor

@aao-release-bot aao-release-bot Bot commented May 30, 2026

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 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.1.0-rc.5

Patch Changes

  • 9ce1a6a: Clarify pre-GA 3.1 RC cleanup notes for removed signal-level GPC and proposal action-mode fields.

    Adds pre-GA adopter guidance for cached requires_proposal action-mode values, reinforces that data_subject_rights.gpc_honored is not part of signal definitions, and documents that projected consent_basis / art9_basis values on get_signals response rows remain provider-declared signal-definition posture rather than seller-substituted basis.

  • a007806: Bump @adcp/sdk to 8.1.0-beta.18 so local and CI storyboard runs enforce
    field_pattern / envelope_field_pattern validations and include required
    task webhook operation_id payloads, then teach the training agent to accept
    the current 3.1-rc.4 wire release pin emitted by that runner.

  • a2b814d: Add storyboard coverage for task webhook operation_id echo semantics. The webhook-emission universal now sends an explicit push_notification_config.operation_id that differs from the runner's URL capture token, validates inbound task webhook payloads against core/mcp-webhook-payload.json, and asserts sellers echo the explicit operation id rather than deriving correlation from the opaque receiver URL.

    Clarifies the webhook receiver runner contract and webhook documentation so URL path routing remains a buyer/runner implementation detail while the payload operation_id is the wire-level correlation field.

Copy link
Copy Markdown
Contributor Author

@aao-release-bot aao-release-bot Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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.

0 participants