Skip to content

fix: get releases into the MCP registry - #6

Merged
dominik1001 merged 2 commits into
mainfrom
fix/release-pipeline
Nov 18, 2026
Merged

dominik1001 merged 2 commits into
mainfrom
fix/release-pipeline

Conversation

@dominik1001

@dominik1001 dominik1001 commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Problems

  1. publish-mcp-registry.yml only runs on release: published. semantic-release creates its GitHub Releases with GITHUB_TOKEN, and events caused by GITHUB_TOKEN don't start other workflows, so automated releases never reach the MCP registry.
  2. The registry rejects server.json: 422 expected length <= 100 on description (it was 105 chars). Seen on the v0.1.0 registry run.

Change

  • release.yml: snapshot the v* tags before semantic-release, output the tag it added (if any), and call the registry workflow in a new mcp-registry job when there is one. Comparing against the snapshot keeps re-runs from re-announcing an old release.
  • publish-mcp-registry.yml: also workflow_call with a version input; checks out the release tag in both paths. The release trigger stays for releases made by hand.
  • server.json: description shortened to 97 chars.

Related fixes outside this diff (already applied)

  • npm trusted publisher configured for release.yml (fixes ENONPMTOKEN)
  • v0.1.0 tag pushed on ce613c2, the commit npm 0.1.0 was published from, plus a GitHub Release for it
  • semantic-release and released labels created so the failure issue / released labels can be applied

Verification

  • PR checks green; workflow YAML parses; tag-detection shell logic checked locally (no new tag → empty, new tag → 0.2.0).
  • Squash-merging with this fix: title cuts 0.1.1, which exercises the whole path end to end: npm publish via trusted publishing, then the mcp-registry job via workflow_call.

🤖 Generated with Claude Code

dominik1001 and others added 2 commits November 18, 2026 10:31
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>
@dominik1001 dominik1001 changed the title ci: publish to the MCP registry after semantic-release releases fix: get releases into the MCP registry Nov 18, 2026
@dominik1001
dominik1001 merged commit 02ab510 into main Nov 18, 2026
10 checks passed
@dominik1001
dominik1001 deleted the fix/release-pipeline branch November 18, 2026 09:35
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))
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions Bot added the released Shipped in a published release label Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released Shipped in a published release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant