Skip to content

Commit

Permalink
fix: make sure goreleaser config matches current schema (#588)
Browse files Browse the repository at this point in the history
Signed-off-by: Marcin Owsiany <[email protected]>
  • Loading branch information
porridge authored Dec 4, 2024
1 parent f0ebf88 commit 532dffe
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
5 changes: 3 additions & 2 deletions .goreleaser.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
version: 2
env:
- GO111MODULE=on
- CGO_ENABLED=0
Expand Down Expand Up @@ -68,7 +69,7 @@ brews:
name: kudoreleasebot
email: [email protected]
skip_upload: auto
folder: Formula
directory: Formula
homepage: https://kuttl.dev
description: Interact with KUTTL via the kubectl plugin
dependencies:
Expand All @@ -78,7 +79,7 @@ brews:
checksum:
name_template: "checksums.txt"
snapshot:
name_template: "{{ .Tag }}-next"
version_template: "{{ .Tag }}-next"

release:
github:
Expand Down
1 change: 1 addition & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ The KUTTL Project is aiming to do monthly minor releases but the period could be
1. Every release should have an appointed release manager (RM)
1. RM is responsible for following the process below
1. RM should announce the release in the public [#kudo slack channel](https://kubernetes.slack.com/messages/kudo/) at least two days prior to the date
1. RM should make sure the installed `goreleaser` is compatible with the checked-in configuration, by running `goreleaser check` and `goreleaser healthcheck`
1. RM makes sure all PRs that need to go into the release are:
1. labeled with the `release/*` labels as appropriate (the release drafter GitHub Action depends on these)
2. merged prior to the process starting
Expand Down

0 comments on commit 532dffe

Please sign in to comment.