From 532dffee0e300ce1023fffbe3657d5a31bd16919 Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Wed, 4 Dec 2024 11:57:42 +0100 Subject: [PATCH] fix: make sure goreleaser config matches current schema (#588) Signed-off-by: Marcin Owsiany --- .goreleaser.yml | 5 +++-- RELEASE.md | 1 + 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.goreleaser.yml b/.goreleaser.yml index 20d09196..0df6742e 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -1,3 +1,4 @@ +version: 2 env: - GO111MODULE=on - CGO_ENABLED=0 @@ -68,7 +69,7 @@ brews: name: kudoreleasebot email: release@kudo.dev skip_upload: auto - folder: Formula + directory: Formula homepage: https://kuttl.dev description: Interact with KUTTL via the kubectl plugin dependencies: @@ -78,7 +79,7 @@ brews: checksum: name_template: "checksums.txt" snapshot: - name_template: "{{ .Tag }}-next" + version_template: "{{ .Tag }}-next" release: github: diff --git a/RELEASE.md b/RELEASE.md index 08ab70c5..bc5baf78 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -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