Version Packages

[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 publish to npm yourself or setup this action to publish 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

adcontextprotocol@2.5.1

Patch Changes

• 72a5802: Fix semantic version sorting for agreements. When multiple agreement versions share the same effective date, the system now correctly selects the highest version (e.g., 1.1.1 before 1.1).

• 935eb43: Fix JSON Schema validation failures when using allOf composition with additionalProperties: false.

  Schemas using allOf to compose with base schemas (dimensions.json, push-notification-config.json) were failing AJV validation because each sub-schema independently rejected the other's properties.

  Fixed schemas:

  • dimensions.json - removed additionalProperties: false (composition-only schema)
  • push-notification-config.json - removed additionalProperties: false (used via allOf in reporting_webhook)
  • video-asset.json - inlined width/height properties, removed allOf
  • image-asset.json - inlined width/height properties, removed allOf

  Added:

  • New test:composed script to validate data against schemas using allOf composition
  • Added to CI pipeline to prevent regression
  • Bundled (dereferenced) schemas at /schemas/{version}/bundled/ for tools that don't support $ref resolution

  Fixes allOf + additionalProperties: false in asset schemas causes validation failures for official examples #275.

• 10d5b6a: Fix analytics dashboard revenue tracking with Stripe webhook customer linkage

• 64b08a1: Redesign how AdCP handles push notifications for async tasks. The key change is separating what data is sent (AdCP's responsibility) from how it's delivered (protocol's responsibility).

  Renamed:

  • webhook-payload.json → mcp-webhook-payload.json (clarifies this envelope is MCP-specific)

  Created:

  • async-response-data.json - Union schema for all async response data types
  • Status-specific schemas for working, input-required, and submitted statuses

  Deleted:

  • Removed redundant -async-response-completed.json and -async-response-failed.json files (6 total)
  • For completed/failed, we now use the existing task response schemas directly

  Before: The webhook spec tried to be universal, which created confusion about how A2A's native push notifications fit in.

  After:

  • MCP uses mcp-webhook-payload.json as its envelope, with AdCP data in result
  • A2A uses its native Task/TaskStatusUpdateEvent messages, with AdCP data in status.message.parts[].data
  • Both use the exact same data schemas - only the envelope differs

  This makes it clear that AdCP only specifies the data layer, while each protocol handles delivery in its own way.

  Schemas:

  • static/schemas/source/core/mcp-webhook-payload.json (renamed + simplified)

  • static/schemas/source/core/async-response-data.json (new)

  • static/schemas/source/media-buy/*-async-response-*.json (6 deleted, 9 remain)

  • Clarified that both MCP and A2A use HTTP webhooks (A2A's is native to the spec, MCP's is AdCP-provided)

  • Fixed webhook trigger rules: webhooks fire for all status changes if pushNotificationConfig is provided and the task runs async

  • Added proper A2A webhook payload examples (Task vs TaskStatusUpdateEvent)

  • Task Management added to sidebar, it was missing