Version Packages - #93
Merged
Merged
Conversation
tuyakhov
approved these changes
Jul 31, 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
@senderkit/cli@0.9.0
Minor Changes
ca9d5ec: MCP manifest fixes from the 2026-07-31 connectors-directory audit — the shared
manifest now states the real wire contract, so the hosted server no longer needs
app-side overrides for these:
ToolAnnotationswidened to admit non-destructive writes. The union wasreadOnlyHint: trueXORdestructiveHint: true, but MCP also has additive,non-destructive writes (
destructiveHint: false) — e.g. the app'stemplates_create/inbound_addresses_create.destructiveHintnow acceptseither boolean (still exactly one hint per tool).
these fields are plain JSON arrays; "(CLI: comma-separated or JSON array)" is
gone from the manifest, and the schema now also enforces the API's 50-recipient
cap (
maxItems: 50). The CLI keeps documenting comma-separated input in itsown flag help via the new
Command.flagHelpper-flag override.messagesListInput.limitadvertises the serviceclamp (1-200, default 50) instead of an unbounded positive int, and
inboundMessagesListInput.limitnow enforces the 1-100 bounds its descriptionalready claimed. Out-of-range values fail at the schema instead of being
silently clamped server-side.
Patch Changes
@senderkit/sdk@0.14.0
Minor Changes
ca9d5ec: MCP manifest fixes from the 2026-07-31 connectors-directory audit — the shared
manifest now states the real wire contract, so the hosted server no longer needs
app-side overrides for these:
ToolAnnotationswidened to admit non-destructive writes. The union wasreadOnlyHint: trueXORdestructiveHint: true, but MCP also has additive,non-destructive writes (
destructiveHint: false) — e.g. the app'stemplates_create/inbound_addresses_create.destructiveHintnow acceptseither boolean (still exactly one hint per tool).
these fields are plain JSON arrays; "(CLI: comma-separated or JSON array)" is
gone from the manifest, and the schema now also enforces the API's 50-recipient
cap (
maxItems: 50). The CLI keeps documenting comma-separated input in itsown flag help via the new
Command.flagHelpper-flag override.messagesListInput.limitadvertises the serviceclamp (1-200, default 50) instead of an unbounded positive int, and
inboundMessagesListInput.limitnow enforces the 1-100 bounds its descriptionalready claimed. Out-of-range values fail at the schema instead of being
silently clamped server-side.
@senderkit-examples/nextjs-basic@0.0.15
Patch Changes
@senderkit-examples/node-basic@0.0.15
Patch Changes