Skip to content

ci: release from a manual Release workflow run on main - #54

Merged
fatwang2 merged 1 commit into
mainfrom
claude/dispatch-release
Oct 26, 2026
Merged

fatwang2 merged 1 commit into
mainfrom
claude/dispatch-release

Conversation

@fatwang2

Copy link
Copy Markdown
Member

Before: publishing a version required someone to create a GitHub Release by hand. A manual run of the Release workflow only re-synced the MCP Registry.

After: running the Release workflow on main releases the version in package.json. It publishes to npm, creates the v<version> GitHub Release and syncs the MCP Registry. Each step skips what already exists, so re-running after a partial failure fills in only what is missing. Publishing a GitHub Release by hand still works.

How: the publish job no longer requires the release event, a new github-release job creates the Release with GITHUB_TOKEN (which does not start the workflow a second time), and a manual run outside main fails in verify.


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7jAP9YsE7D4HvphbaKNCc
@fatwang2
fatwang2 merged commit 70dbd01 into main Oct 26, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants