Skip to content

chore: mark prerelease tags automatically in GoReleaser - #108

Merged
yvonnedevlinrh merged 1 commit into
unbound-force:mainfrom
yvonnedevlinrh:chore/goreleaser-prerelease-auto
Aug 24, 2026
Merged

chore: mark prerelease tags automatically in GoReleaser#108
yvonnedevlinrh merged 1 commit into
unbound-force:mainfrom
yvonnedevlinrh:chore/goreleaser-prerelease-auto

Conversation

@yvonnedevlinrh

Copy link
Copy Markdown
Contributor

Summary

Add prerelease: auto to .goreleaser.yaml so GoReleaser automatically detects semver prerelease suffixes (-rc.N, -alpha.N, -beta.N) and sets the GitHub release prerelease flag accordingly.

Problem

Prerelease tags (e.g., v3.1.0-rc.1) would be published as full releases. This means brew upgrade would 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., v3.1.0) continue to be marked as full releases.

Mirrors unbound-force/gaze#232.

@yvonnedevlinrh
yvonnedevlinrh requested a review from a team August 21, 2026 10:11
@yvonnedevlinrh yvonnedevlinrh self-assigned this Aug 21, 2026
@yvonnedevlinrh yvonnedevlinrh moved this to Ready for Review 👀 in Unbound Force Planning Aug 21, 2026

@em-redhat em-redhat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Add prerelease: auto to release config so GoReleaser detects
semver prerelease suffixes (-rc, -alpha, -beta) and sets the
GitHub release prerelease flag accordingly.
@yvonnedevlinrh
yvonnedevlinrh force-pushed the chore/goreleaser-prerelease-auto branch from 247da3f to eca4049 Compare August 24, 2026 09:51
@yvonnedevlinrh
yvonnedevlinrh merged commit ffbd5d3 into unbound-force:main Aug 24, 2026
2 checks passed
@yvonnedevlinrh
yvonnedevlinrh deleted the chore/goreleaser-prerelease-auto branch August 24, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready for Review 👀

Development

Successfully merging this pull request may close these issues.

3 participants