Skip to content

ci: dispatch MCP publish after site-release version bump - #409

Merged
ShixiangWang merged 1 commit into
mainfrom
ci/site-release-dispatch-mcp
Oct 18, 2026
Merged

ShixiangWang merged 1 commit into
mainfrom
ci/site-release-dispatch-mcp

Conversation

@ShixiangWang

Copy link
Copy Markdown
Member

Problem

Site Release pushes the version bump with GITHUB_TOKEN. GitHub suppresses downstream workflow runs for such pushes, so mcp-publish.yml never ran for the automated v1.1.1 bump commit (8d4fdd6), leaving npm at 0.2.0.

Change

  • Add actions: write.
  • Dispatch mcp-publish.yml explicitly after pushing the bump commit. The publish workflow is idempotent: it skips versions already on npm and tags that already exist.

Verification

  • YAML parses.
  • Observed the failure mode on v1.1.1: Site Release succeeded, the bump commit landed, and no MCP Publish run was created; 1.1.1 was published with a manual workflow_dispatch.
  • This change makes the next tag self-contained.

🤖 Generated with Claude Code

Pushes made with GITHUB_TOKEN do not trigger downstream workflows, so
mcp-publish.yml never ran for the automated v1.1.1 bump commit. Dispatch
it explicitly; the publish workflow is idempotent and skips versions
already present on npm.
@github-actions

Copy link
Copy Markdown
Contributor

✅ QMD Format Check

No new QMD tutorial files to check.

@ShixiangWang
ShixiangWang merged commit 3661b4d into main Oct 18, 2026
4 checks passed
@ShixiangWang
ShixiangWang deleted the ci/site-release-dispatch-mcp branch October 18, 2026 14:28
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.

1 participant