Repository navigation
meta: Merge release/cli/0.49.0 and bump to 0.50.0-dev.0 - #2082
Closed
sentry-junior[bot] wants to merge 4 commits into
Closed
sentry-junior[bot] wants to merge 4 commits into
sentry-junior[bot] wants to merge 4 commits into
Conversation
The MCP Registry drops false booleans from a listing, so after #1986 spelled out isRequired: false and isSecret: false, the listing no longer deep-equals server.json. Craft's mcp-registry target checks exactly that after publishing, so the 0.49.0 publish failed there, and a retry fails the same check against the existing listing. Leave the fields out (false is their default) and add a server.json check that keeps them out. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
This branch was successfully deployed
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 finishes the CLI 0.49.0 release, like #2028 did for 0.48.0. Every publish target shipped (publish issue). Craft couldn't push the release branch merge to
main, because themainrulesets require a pull request (job log). So the post-release bump didn't run either.This PR
release/cli/0.49.0intomain, with no conflicts. That brings in the 0.49.0CHANGELOG.mdsection, the release versions, and theserver.jsonfix from fix(mcp): Leave false defaults out of the MCP Registry manifest (0.49.0) #2080.postReleaseBumpdoes: the npm bump plusversioning.filesfrom.craft.yml.packages/cli/package.jsonandpackages/mcp-server/package.json→0.50.0-dev.0SKILL.md,references/*.md) →0.50.0-dev.0.claude-plugin/plugin.json→0.50.0(stripPrerelease)#2080 brings in the same
server.jsonchange as #2079, so #2079 has nothing left to add once this merges.Keep
release/cli/0.49.0until this merges. After that, close the publish issue rather than addingacceptedagain: after a squash merge, a retry fails the same way.via @BYK.
--
View Session in Sentry