ci(release): auto-push version tag on merge to main#16
Merged
Conversation
Removes the manual `git tag mcp-v<ver> && git push` step that was getting forgotten between the version-bump PR landing and the actual npm publish (0.2.2 sat on main for hours before someone noticed). How: new `auto-tag.yml` triggers on push to main when either `packages/mcp/package.json` or `packages/leadclaw/package.json` changes, reads the version, and pushes `<pkg>-v<ver>` if that tag doesn't already exist. Existing `release.yml` then fires on the tag push (unchanged). Idempotent: re-runs on the same version no-op. Updated `release.yml` header comment so the runbook reflects automatic tagging rather than the old manual `git tag` recipe. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Removes the manual `git tag` step between landing a version bump and the actual npm publish — the gap that left 0.2.2 sitting unreleased on main for hours.
New `auto-tag.yml` triggers on push to main when either package's `package.json` changes, reads the version, and pushes `-v` (mcp or leadclaw) if that tag doesn't already exist. Existing `release.yml` then fires on the tag push — no changes to the working publish pipeline. Idempotent: re-runs on the same version no-op.
Test plan
🤖 Generated with Claude Code