Skip to content

Commit

Permalink
fix: correctly set prerelease flag (#1085)
Browse files Browse the repository at this point in the history
<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it

Currently all releases (even if candidates) were published as the latest
release even though they should be marked as prereleases. This changes
this by using the correct goreleaser indicator:

```
  # If set to auto, will mark the release as not ready for production
  # in case there is an indicator for this in the tag e.g. v1.0.0-rc1
  # If set to true, will mark the release as not ready for production.
  # Default: false.
```

#### Which issue(s) this PR fixes
<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
  • Loading branch information
jakobmoellerdev authored Nov 13, 2024
1 parent c55fe22 commit b387386
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions .github/config/goreleaser.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
# However, latest builds (equivalent to nightlies based on the main branch), uses latest.yml
version: 2

release:
prerelease: auto

before:
hooks:
- go mod tidy
Expand Down

0 comments on commit b387386

Please sign in to comment.