chore: mark prerelease tags automatically in GoReleaser - #83
Open
yvonnedevlinrh wants to merge 1 commit into
Open
chore: mark prerelease tags automatically in GoReleaser#83yvonnedevlinrh wants to merge 1 commit into
yvonnedevlinrh wants to merge 1 commit into
Conversation
Add prerelease: auto to release config so GoReleaser detects semver prerelease suffixes (-rc, -alpha, -beta) and sets the GitHub release prerelease flag accordingly.
yvonnedevlinrh
added
the
github_actions
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
2 participants
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
Add
prerelease: autoto.goreleaser.yamlso GoReleaser automatically detects semver prerelease suffixes (-rc.N,-alpha.N,-beta.N) and sets the GitHub releaseprereleaseflag accordingly.Problem
Prerelease tags (e.g.,
v1.0.0-rc.1) would be published as full releases. This meansbrew upgradewould install them as the latest stable version, and the GitHub releases page shows them alongside stable releases without distinction.Change
One-line addition to the existing
release:block in.goreleaser.yaml. Stable tags (e.g.,v1.0.0) continue to be marked as full releases.