Version Packages - #101
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 10, 2026 08:04
e730db3 to
7512dd4
Compare
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.3
Patch Changes
dc37adf: Sharpen the send-tool schema guidance to match the hosted API's validation, so MCP agents and CLI users get the constraint before they hit a
400:scheduledAtnow documents that the timestamp must be in the future and at most 30 days ahead (with a reminder to check the current date first). This flows through bothsenderkit_sendandsenderkit_send_raw, their CLI help, and the SDK README's scheduling section.senderkit_send_rawsubjectandhtmlnow state that they are required when the channel isemail— a text-only email send is rejected, so plain text should be wrapped in minimal HTML.Updated dependencies [dc37adf]
@senderkit/sdk@0.14.3
Patch Changes
dc37adf: Sharpen the send-tool schema guidance to match the hosted API's validation, so MCP agents and CLI users get the constraint before they hit a
400:scheduledAtnow documents that the timestamp must be in the future and at most 30 days ahead (with a reminder to check the current date first). This flows through bothsenderkit_sendandsenderkit_send_raw, their CLI help, and the SDK README's scheduling section.senderkit_send_rawsubjectandhtmlnow state that they are required when the channel isemail— a text-only email send is rejected, so plain text should be wrapped in minimal HTML.@senderkit-examples/nextjs-basic@0.0.18
Patch Changes
@senderkit-examples/node-basic@0.0.18
Patch Changes