Repository navigation
ci(release): release on a pushed v* tag - #8
Merged
Merged
Conversation
Pushing a v* tag now creates the GitHub release from that version's CHANGELOG section and runs the same packaging, server.json and Homebrew steps. Uploads use --clobber and the tap commit is skipped when the formula is unchanged, so a rerun for the same tag is safe. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EtxtFPs6UBAWXqEpkj2W2N
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
xcforge-web | a057d01 | Oct 10 2026, 01:24 AM |
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
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.
Before: a release only went out when someone published it in GitHub's UI, which then built the tarball and .mcpb, updated server.json and pushed the Homebrew formula.
After: pushing a
v*tag does the same thing end to end. The job creates the GitHub release itself, using that version's CHANGELOG section as the notes, and then runs the existing steps. Publishing from the UI still works exactly as before.How: adds a
push: tags: ['v*']trigger and a first step that runsgh release create --verify-tagwhen the release doesn't exist yet. A release created with GITHUB_TOKEN doesn't firerelease: published, so one tag never triggers two runs, and a per-tag concurrency group covers the rest. Asset upload now uses--clobberand the tap commit is skipped when the formula hasn't changed, so rerunning a tag is safe. The CHANGELOG extraction was checked locally against the 1.6.1 section.🤖 Generated with Claude Code
https://claude.ai/code/session_01EtxtFPs6UBAWXqEpkj2W2N
Generated by Claude Code