fix(ci): restore v0.1.{run_number} release tags and drop prerelease flag for main builds#31
Merged
Merged
Conversation
…lag for main builds Agent-Logs-Url: https://github.com/InterestingSoftware/SproutGit/sessions/78171281-d581-42d0-843b-e359bf7ec6b6 Co-authored-by: liam-russell <17897133+liam-russell@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
liam-russell
May 19, 2026 03:22
View session
liam-russell
approved these changes
May 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR restores the main-branch CI release behavior to publish stable v0.1.{run_number} releases instead of main-{run_number} prereleases.
Changes:
- Uses
v0.1.{github.run_number}as the generated tag for main builds. - Removes the explicit release
name, allowing it to default to the tag. - Marks releases as prerelease only when the ref name contains
-.
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.
The electron branch merge replaced the original
v0.1.{run_number}non-prerelease tagging scheme withmain-{run_number}prereleases, breaking the per-build release cadence established by the Tauri-era CI.Changes
main-{run_number}→v0.1.{run_number}for main branch builds, restoring thev0.1.173-style releasesgithub.ref == 'refs/heads/main'from the condition —prereleaseis now solelycontains(github.ref_name, '-'), so stable main builds and unadornedv*tags produce full releases; only tags likev1.0.0-betaare marked pre-releasename:field — defaults to the tag name, matching prior behavior