Version Packages (rc)#5217
Open
aao-release-bot[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
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.
1aa4ecc to
2ed44b2
Compare
2ed44b2 to
d7ed533
Compare
d7ed533 to
a650826
Compare
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
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 main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.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_proposalaction-mode values, reinforces thatdata_subject_rights.gpc_honoredis not part of signal definitions, and documents that projectedconsent_basis/art9_basisvalues onget_signalsresponse rows remain provider-declared signal-definition posture rather than seller-substituted basis.a007806: Bump
@adcp/sdkto8.1.0-beta.18so local and CI storyboard runs enforcefield_pattern/envelope_field_patternvalidations and include requiredtask webhook
operation_idpayloads, then teach the training agent to acceptthe current
3.1-rc.4wire release pin emitted by that runner.a2b814d: Add storyboard coverage for task webhook
operation_idecho semantics. The webhook-emission universal now sends an explicitpush_notification_config.operation_idthat differs from the runner's URL capture token, validates inbound task webhook payloads againstcore/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_idis the wire-level correlation field.