Repository navigation
fix: get releases into the MCP registry - #6
Merged
Merged
Conversation
semantic-release creates the GitHub Release with GITHUB_TOKEN, and events caused by GITHUB_TOKEN never start other workflows, so the `release: published` trigger in publish-mcp-registry.yml never fired for automated releases. release.yml now detects the tag semantic-release created and calls the registry workflow directly; the `release` trigger stays for releases made by hand. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…imit The registry rejected 0.1.0 with 422 "expected length <= 100" on body.description (it was 105 characters). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Nov 18, 2026
## [0.1.1](v0.1.0...v0.1.1) (2026-11-18) ### Bug Fixes * get releases into the MCP registry ([#6](#6)) ([02ab510](02ab510))
|
🎉 This PR is included in version 0.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Problems
publish-mcp-registry.ymlonly runs onrelease: published. semantic-release creates its GitHub Releases withGITHUB_TOKEN, and events caused byGITHUB_TOKENdon't start other workflows, so automated releases never reach the MCP registry.server.json:422 expected length <= 100ondescription(it was 105 chars). Seen on the v0.1.0 registry run.Change
release.yml: snapshot thev*tags beforesemantic-release, output the tag it added (if any), and call the registry workflow in a newmcp-registryjob when there is one. Comparing against the snapshot keeps re-runs from re-announcing an old release.publish-mcp-registry.yml: alsoworkflow_callwith aversioninput; checks out the release tag in both paths. Thereleasetrigger stays for releases made by hand.server.json: description shortened to 97 chars.Related fixes outside this diff (already applied)
release.yml(fixesENONPMTOKEN)v0.1.0tag pushed once613c2, the commit npm 0.1.0 was published from, plus a GitHub Release for itsemantic-releaseandreleasedlabels created so the failure issue / released labels can be appliedVerification
0.2.0).fix:title cuts 0.1.1, which exercises the whole path end to end: npm publish via trusted publishing, then themcp-registryjob viaworkflow_call.🤖 Generated with Claude Code