You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- CHANGELOG.md: promote Unreleased to 0.3.0 with today's date and
a full summary of the signing, SBOM, attestation, installer,
docs, and Go-cleanup changes shipping in this release.
- README.md and docs/install.sh: bump the version pinning
examples from v0.1.6 / v0.2.0 to v0.3.0.
- CONTRIBUTING.md: update the release process examples to reference
v0.3.0 instead of v0.2.0.
- docs/install.test.sh intentionally still pins TEST_VERSION to
v0.2.0 to exercise the installer's legacy-release soft-skip
path (v0.2.0 predates cosign signing).
GoReleaser is mostly idempotent, but a partial failure (for example a tap push rejected) leaves the GitHub Release in place while the tap cask is out of date. To redo cleanly:
154
154
155
155
```sh
156
-
gh release delete v0.2.0 -y
157
-
git push origin :refs/tags/v0.2.0
158
-
git tag -d v0.2.0
156
+
gh release delete v0.3.0 -y
157
+
git push origin :refs/tags/v0.3.0
158
+
git tag -d v0.3.0
159
159
160
160
# Fix the problem in a new commit, push to main, then retag from the fixed commit.
161
-
git tag -a v0.2.0 -m "v0.2.0 - ..."
162
-
git push origin v0.2.0
161
+
git tag -a v0.3.0 -m "v0.3.0 - ..."
162
+
git push origin v0.3.0
163
163
```
164
164
165
165
Do **not** re-tag a version that has already propagated to `proxy.golang.org` — the proxy caches tagged module versions forever. Bump the patch version (`v0.2.1`) instead.
0 commit comments