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 2.6.x, this PR will be updated.
Releases
adcontextprotocol@2.7.0
Minor Changes
e2b0b62: Add unified
assetsfield to format schema for better asset discoveryassetsarray to format schema withrequiredboolean per assetassets_required(still supported for backward compatibility)5cd83b8: Add Property Governance Protocol support to get_products
property_listparameter to get_products request for filtering products by property listproperty_list_appliedresponse field to indicate whether filtering was appliedPatch Changes
309a880: Allow additional properties in all JSON schemas for forward compatibility
Changes all schemas from
"additionalProperties": falseto"additionalProperties": true. This enables clients running older schema versions to accept responses from servers with newer schemas without breaking validation - a standard practice for protocol evolution in distributed systems.5d0ce75: Add explicit type definition to error.json details property
The
detailsproperty in core/error.json now explicitly declares"type": "object"and"additionalProperties": true, consistent with other error details definitions in the codebase. This addresses issue core/error.json doesn't specify data type of the "details" property #343 where the data type was unspecified.cdcd70f: Fix migration 151 to delete duplicates before updating Slack IDs to WorkOS IDs
39abf79: Add missing fields to package request schemas for consistency with core/package.json.
Schema Changes:
media-buy/package-request.json: Addedimpressionsandpausedfieldsmedia-buy/update-media-buy-request.json: Addedimpressionsfield to package updatesDetails:
impressions: Impression goal for the package (optional, minimum: 0)paused: Create package in paused state (optional, default: false)These fields were defined in
core/package.jsonbut missing from the request schemas, making it impossible to set impression goals or initial paused state when creating/updating media buys.Documentation:
create_media_buytask reference with new package parametersupdate_media_buytask reference with impressions parameterfa68588: fix: display Slack profile name for chapter leaders without WorkOS accounts
Leaders added via Slack ID that haven't linked their WorkOS account now display
their Slack profile name (real_name or display_name) instead of the raw Slack
user ID (e.g., U09BEKNJ3GB).
The getLeaders and getLeadersBatch queries now include slack_user_mappings as an
additional name source in the COALESCE chain.
9315247: Release schemas with
additionalProperties: truefor forward compatibilityThis releases
dist/schemas/2.5.2/containing the relaxed schema validationintroduced in Allow additional properties in all JSON schemas #646. Clients can now safely ignore unknown fields when parsing
API responses, allowing the API to evolve without breaking existing integrations.