Version Packages (beta)

[github-actions]

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

The changelog information of each package has been omitted from this message, as the content exceeds the size limit.

adcontextprotocol@3.1.0-beta.0

[desiorac]

The committed_metrics snapshot design closes an audit gap that most implementations ignore until a dispute surfaces it: without a buy-time freeze, the "binding contract" is implicitly the product's current available_metrics, which mutates. Auditing a 90-day-old buy against current state produces a meaningless result.

One open question on the RBAC lifecycle: the 300s refresh normative for authorization defines load-balanced flicker as non-conformant, but leaves buyer behavior unspecified when SCOPE_INSUFFICIENT arrives within that window. Is the intended behavior correctable-with-retry (assume transient inconsistency) or surface-immediately (assume legitimate scope reduction)? The spec says correctable but NOT agent-autonomous - clarifying whether the retry window tracks the 300s refresh cadence would remove the ambiguity.

[bokelley]

Thanks @desiorac — both points are real, and #3490 is the auto-generated Changesets release PR so neither belongs here. Splitting them out:

• committed_metrics snapshot design — your framing of the audit-gap motivation is exactly right; if there's spec text you'd want sharpened (e.g., explicit binding-contract language tying audit semantics to the snapshot rather than current available_metrics), open an issue and we'll pull it in.
• SCOPE_INSUFFICIENT retry semantics within the 300s window — filed as Clarify buyer retry semantics for SCOPE_INSUFFICIENT within the 300s authorization refresh window #3674 with a starting proposal (bounded retry with backoff, then surface; retry budget is not the 300s propagation SLA). Continuing there.

Closing this thread out from the release PR.