Release v0.8.0

.goreleaser.yaml

@@ -1,6 +1,3 @@
-gomod:
-  proxy: true
-
 builds:
   - env:
       - CGO_ENABLED=0

CHANGELOG.md

@@ -7,7 +7,9 @@ The sections should follow the order `Added`, `Changed`, `Fixed`, `Removed`, and
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased](https://github.com/sapcc/absent-metrics-operator/compare/v0.7.3...HEAD)
+## [Unreleased](https://github.com/sapcc/absent-metrics-operator/compare/v0.8.0...HEAD)
+
+## 0.8.0 - 2022-04-12
 
 ### Added
 

RELEASE.md

@@ -3,13 +3,16 @@
 1. Ensure local `master` branch is up to date with `origin/master`.
 2. Ensure all checks are passing: `make check`.
 3. Update the [`CHANGELOG`](./CHANGELOG.md) as appropriate. Make sure that the format is
-   consistent (especially the version heading).
-4. Commit the updated changelog.
-5. Create and push a new Git tag (`v[0-9]+.[0-9]+.[0-9]+`). We follow [semantic
-   versioning][semver] for our tags/releases. A [lightweight tag][lightweight-tags] is
-   sufficient as GoReleaser will update the release description using the release notes
-   generated by [release-info].
+   consistent especially the version heading. We follow [semantic versioning][semver] for
+   our releases.
+4. Commit the updated changelog with message: `Release <version>`
+5. Create and push a new Git tag: note that tags are prefixed with `v` and the GitHub
+   release workflow is triggered for tags that match the `v[0-9]+.[0-9]+.[0-9]+`
+   [pattern][gh-pattern].  A [lightweight tag][lightweight-tags] is sufficient as
+   GoReleaser will update the release description using the release notes generated by
+   [release-info].
 
 [release-info]: https://github.com/sapcc/go-bits/tree/master/tools/release-info
 [lightweight-tags]: https://git-scm.com/book/en/v2/Git-Basics-Tagging#_lightweight_tags
 [semver]: https://semver.org/spec/v2.0.0.html
+[gh-pattern]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#patterns-to-match-branches-and-tags