Repository navigation
ci(release): skip the tag-push run when the release already exists - #10
Merged
Merged
Conversation
Publishing a release on GitHub creates its tag, which also fires the push trigger. That run queued behind the release run and would rebuild and re-upload the assets. It now stops once it sees the release exists. 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 | 6ce311b | Oct 10 2026, 03:52 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: publishing a release on GitHub created its tag, and that tag push started a second Release run. It queued behind the real one, then rebuilt the binary, re-uploaded the assets and pushed the Homebrew formula again. That happened for v1.7.0.
After: the tag-push run sees the release already exists and stops after its first step. A tag pushed without a release still creates the release and publishes it, as before.
How: the create step records
skip=truewhen the release exists, and every later step checks it.🤖 Generated with Claude Code
https://claude.ai/code/session_01EtxtFPs6UBAWXqEpkj2W2N
Generated by Claude Code