ci: auto-publish MCP server on version bump (+ auto-tag)#207
Merged
Conversation
The MCP publish was tag-triggered only, and 20 version bumps (2.3 -> 2.22) were committed without a matching mcp-v* tag ever being pushed -- so npm sat 20 versions behind the repo and agents couldn't see new tools (facets/count/graph/ novelty/etc.). This prevents recurrence. - New mcp-autopublish.yml: on any master push that changes mcp-server/package.json, if that version isn't already on npm, publish it (--provenance) and create + push the mcp-v<version> record tag automatically. Self-contained (NPM_TOKEN); guards on already-published so it's a no-op when nothing changed. - npm-publish.yml (manual tag escape hatch) gains the same already-published guard, so re-tagging an existing release is a no-op instead of a hard failure, and the two workflows can never double-fail on a race.
mkreyman
added a commit
that referenced
this pull request
Jun 29, 2026
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.
Why
The MCP publish was tag-triggered only. Twenty version bumps (2.3 → 2.22) were committed without anyone pushing a matching
mcp-v*tag, so npm sat 20 versions behind the repo and agents couldn't see new tools. We just hit and fixed that manually (published 2.22.0); this prevents it from ever happening again.What
mcp-autopublish.yml— on any master push that changesmcp-server/package.json, if that version isn't already on npm, publish it (--provenance) and create + push themcp-v<version>record tag automatically. Self-contained (usesNPM_TOKEN), and guards on already-published so it's a no-op when the version is unchanged. (Auto-tag included, per request.)npm-publish.yml(the manual tag escape hatch) gains the same already-published guard, so re-tagging an existing release is a no-op instead of a hard failure — and the two workflows can never double-fail on a race.Verification
Both workflows YAML-validated. The behavior is verifiable on the next
mcp-server/package.jsonbump (next P3 / MCP change) — it should publish + tag with no manual step.