Repository navigation
[Discovery] Publish to the MCP Registry after each stable release #1132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Aymericr
merged 5 commits into
main
from
cursor/mcp-registry-publish-after-release-53c2
Oct 27, 2026
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e38db49
Publish server.json to the MCP Registry after each stable release
cursoragent 6f4f30d
Merge branch 'main' into cursor/mcp-registry-publish-after-release-53c2
Aymericr a7ac759
Merge remote-tracking branch 'origin/main' into cursor/mcp-registry-p…
cursoragent 04c9e4c
MCP Registry publish: validate the manifest against fixed values, sco…
cursoragent d2e96ca
MCP Registry publish: pin the validated commit and repeat the full check
cursoragent File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a partial beta release is recovered with the documented
bump=none, the release keeps its*-beta.*version butNPM_TAG/thechanneloutput is set tolatestbecause only the literalbetainput selects the beta channel. This condition therefore invokes the registry workflow with the prerelease version, whilesync-agent-versions.tsintentionally leavesserver.jsonon the previous stable version; the called workflow then fails itsVERSION != EXPECTED_VERSIONcheck. A recovery that otherwise successfully publishes or tags the beta is consequently reported failed. Gate this job on the released version containing no prerelease suffix, or expose an explicit stable-release output instead of inferring stability fromchannel.Useful? React with 👍 / 👎.