chore: release package#2359
Merged
Merged
Conversation
aao-ipr-bot
Bot
force-pushed
the
changeset-release/main
branch
from
July 14, 2026 19:33
9ea08ef to
58fc170
Compare
andybevan-scope3
approved these changes
Jul 15, 2026
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.
Releases
@adcp/sdk@12.0.0
Major Changes
5a38f85: Add MCP 2026-07-28 client negotiation and dual-era HTTP serving through the official v2 SDK while retaining the v1 path for legacy peers and 2025 Tasks compatibility. High-level endpoint discovery, tool listing, and OAuth calls now negotiate the modern era; modern requests reject cross-origin redirects, do not replay failed tool calls, and fail closed on malformed JSON. Host/Origin validation now protects framework-owned AdCP servers before era classification, so it applies to legacy and modern traffic: public deployments must configure
publicUrlor explicitallowedHosts/allowedOrigins, including an upstream hostname when a reverse proxy rewritesHost. Raw v1McpServerinstances remain legacy-only so resources, prompts, and Tasks extras are preserved. Raise the minimum supported Node.js version to 20, as required by MCP SDK v2.1053705: Ship a tree-shakeable dual ESM + CJS build.
The library now builds with tsup (
bundle: false, one output file per sourcemodule), emitting ESM (
.mjs, reached via theimportcondition) alongside theexisting CommonJS (
.js, reached viarequire), and declaressideEffectssobundlers can drop unused code. Importing a single symbol no longer pulls the
whole barrel:
import { EventTypeValues } from '@adcp/sdk/types'bundles tounder 1 KB with zod absent, down from ~1.9 MB.
require('@adcp/sdk')and the CLI keep working. This is a major version becauseevery consumer's module resolution goes through the reworked
exportsmap(each subpath now resolves
import→.mjs,require→.js,types→.d.ts).The
@a2a-js/sdkpeer floor is raised from^0.3.4to^0.3.13:@adcp/sdk/serverimports
agentCardHandlerfrom@a2a-js/sdk/server/express, which only existsfrom 0.3.13. CJS named-import interop masked a too-low pin; ESM surfaces it as a
load-time error, so the floor now matches what the code actually needs.
Dual-package safety: the request-signing and response-capture
AsyncLocalStoragestores are anchored on the global symbol registry so aprocess that loads both builds shares one instance (no silently unsigned
requests), and the verified-signature brand uses
Symbol.for. Consumers thatinstanceof-check SDK errors across a mixed ESM/CJS boundary should use theexported
isADCPError/isErrorOfTypeguards instead.Patch Changes
1053705: Harden the publish artifact and correct a peer-dependency floor.
@modelcontextprotocol/sdkpeer floor from^1.17.5to^1.24.0.The main entry eagerly loads
server/tasks, which imports@modelcontextprotocol/sdk/experimental/tasks/*; those subpaths first ship in1.24.0, so any consumer importing
@adcp/sdkon an older MCP SDK hitERR_MODULE_NOT_FOUND. Same class of too-low pin as the@a2a-js/sdkfix..d.mts) alongside.d.tsand give everysubpath export per-condition types, so the ESM
importcondition no longerresolves to a CJS declaration ("masquerading as CJS").
@adcp/sdk/enums'simportcondition now points atenums.mjs, andenums,testing/personas,and
server/legacy/v5gained thetypesVersionsentries they were missing.Raising the
@modelcontextprotocol/sdkpeer floor is a breaking-shaped change; itis safe here only because it is co-released with the major bump from the
tree-shakeable dual-build changeset.
Verification tooling only (devDependencies, no new runtime deps):
npm run check:package(publint + attw) andnpm run verify:package(clean-roomdual-format smoke against the packed tarball with peers at their range floors),
both wired into CI. See
docs/development/PACKAGE-VERIFICATION.md.@adcp/eslint-plugin@0.1.6
Patch Changes