Version Packages#5232
Merged
Merged
Conversation
![aao-release-bot[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
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.
aao-release-bot
Bot
force-pushed
the
changeset-release/3.0.x
branch
from
dd485fa to
f32f30e
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
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.0.x, this PR will be updated.
Releases
adcontextprotocol@3.0.15
Patch Changes
compliance suite failures:
media_buy_state_machineandmeasurement_terms_rejectednow use forward-looking Q3 2026 windows, theuniversal idempotency missing-key vector no longer depends on a same-day May
flight, the state-machine fixture keeps the existing 3.0.x
statusresponseassertions, and the compliance build rejects stable or duplicate generated
idempotency keys on mutating storyboard steps.
so events exactly five days out do not intermittently render as four days.