fix: draft-then-publish release pattern and version alignment#40
Merged
fix: draft-then-publish release pattern and version alignment#40
Conversation
- Replace single Create Release step with draft-then-publish pattern to avoid GitHub immutable release conflicts on workflow re-runs - No hardcoded version references found; version is purely MinVer-driven Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
KrennicMS
force-pushed
the
fix/release-workflow-and-version
branch
from
07d7708 to
0bc45e2
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions release workflow to better support re-runs on the same tag by switching to a draft-first release flow before publishing, while confirming versioning remains tag/MinVer-driven (no hardcoded version bumps needed).
Changes:
- Create the GitHub Release as a draft while uploading artifacts.
- Publish the release afterward via
actions/github-scriptby flippingdraft: false.
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.
Summary
Two fixes to the release process:
1. Version alignment
Version is purely MinVer-driven from Git tags — no hardcoded
0.5.0references found. Nothing to change here.2. Draft-then-publish release pattern
Replaces the single
Create Releasestep (which would fail on re-runs due to immutable release conflicts) with a two-step pattern:draft: falseviaactions/github-scriptAPI callThis prevents the
tag_name was used by an immutable releaseerror when workflows are re-triggered on the same tag.Files Changed
.github/workflows/release.yml