fix(ci): tag-only release flow + bump to 0.3.1#21
Merged
Conversation
The previous release flow tried to push a chore(release) commit + tag to main from the workflow. With branch protection requiring 2 status checks on every commit pushed to main, that commit (created in the runner) had no CI runs and was always rejected by the protected-branch hook (GH006). Mirror the @vllnt/ui pattern: tag-only releases. - workflow_dispatch loses the `bump` input — version is read from package.json (bumped via PR before dispatch, where CI runs on it). - New "Read version + guard against retag" step fails fast if the tag already exists, preventing the orphan-tag scenario from the prior run. - Drops `git push origin main --follow-tags` — workflow only pushes the vX.Y.Z tag, which isn't branch-protected. Default GITHUB_TOKEN handles it (no PAT needed). - GH release notes go through a notes-file (avoids quoting issues with multi-line bodies passed via --notes "$(...)"). Bump 0.3.0 → 0.3.1 in package.json + CHANGELOG header + the four doc surfaces that hardcode the default MCP server version (src/server.ts, README.md, llms-full.txt, docs/api-reference.md).
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 previous release flow tried to push a `chore(release): vX.Y.Z` commit + tag to `main` from inside the release job. With branch protection on `main` requiring `ci (20)` + `ci (22)` checks on every push, that commit (created by the workflow runner, no CI run against it) was always rejected — `GH006: Protected branch update failed` — leaving an orphan tag and no published release.
Run that hit it: 25018770354. The orphan `v0.3.1` tag from that run is still on origin and needs to be deleted before the next dispatch.
What
Mirror the @vllnt/ui pattern: tag-only releases.
Plus: bump `0.3.0` → `0.3.1` in:
New release procedure
Test plan