Skip to content

fix: replace existing calver release instead of skipping#30

Merged
fredsmith merged 1 commit into
mainfrom
fix/calver-replace-existing
Mar 1, 2026
Merged

fix: replace existing calver release instead of skipping#30
fredsmith merged 1 commit into
mainfrom
fix/calver-replace-existing

Conversation

@fredsmith

Copy link
Copy Markdown
Owner

Summary

  • When a release for today's date already exists, delete it and rebuild instead of skipping
  • Uses gh release delete --cleanup-tag to remove the stale release before building

Why

Multiple pushes to main on the same day caused the version job to output an empty tag (since the release already existed), which skipped the entire build matrix. This meant only the first push of the day produced a release — subsequent merges were silently ignored.

Test plan

  • Merge this PR (which already has a v2026.3.1 release from earlier)
  • Version job should delete v2026.3.1 and re-create it with the latest code
  • All 4 platform builds should run
  • update-cask job should update the cask with fresh sha256 hashes

🤖 Generated with Claude Code

When multiple pushes to main happen on the same day, the version job
was skipping the build because the tag already existed. Now it deletes
the stale release and rebuilds, so the latest code is always released.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@fredsmith fredsmith merged commit ed1f3ac into main Mar 1, 2026
1 check passed
@fredsmith fredsmith deleted the fix/calver-replace-existing branch March 1, 2026 14:19
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