Version Packages (alpha)#151
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
973ebe0 to
df0f77a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
df0f77a to
6346fe6
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
1 participant
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@peekdev/cli@0.1.0-alpha.30
Minor Changes
peek connect add --local <path>to register a locally-built connector (sugar for--command node --args=<abs path>).Patch Changes
@peekdev/mcp@0.1.0-alpha.24
Patch Changes
buildElicitMessagenowproduces a masked, verb-specific sentence (e.g. peek wants to Type "m•••m" into
#emailon your live browser. Approve?) instead of a genericrun "<type>"string. Literal values (typetext,request_user_inputprompt)are masked to the first and last character so no secret is rendered in the
connecting client's chat history. No MCP-contract change — the tool input schema
is unchanged; only the elicitation message text differs.