diff options
| author | Stefan Majewsky <majewsky@gmx.net> | 2026-07-31 23:56:06 +0200 |
|---|---|---|
| committer | Stefan Majewsky <majewsky@gmx.net> | 2026-07-31 23:56:06 +0200 |
| commit | b2e597c7cf7a28b7de7457f1f558511d42f1bc40 (patch) | |
| tree | 3433d0d896d09ad2c723029ae6fbb6983229f1b0 | |
| parent | 238b5820a9968cb4c775fd9cf2e7e2cfeb24c78e (diff) | |
| download | go-oblast-e3c39797ce993f435ad77f45590e23d865da2f9c.tar.gz | |
v0.13.2v0.13.2
| -rw-r--r-- | CHANGELOG.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 0bb1a69..50fa3f1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,10 @@ SPDX-FileCopyrightText: 2026 Stefan Majewsky <majewsky@gmx.net> SPDX-License-Identifier: Apache-2.0 --> +# v0.13.2 (2026-07-31) + +No changes to the previous version. After v0.13.1 also failed, I noticed that `git clone` on the primary repo fails with `Cannot obtain needed object 96727093c88e5db251c55eda31700bf67c832ce1 while processing commit 238b5820a9968cb4c775fd9cf2e7e2cfeb24c78e.`, the former being the digest of the `v0.1.0` tag object. No idea why, but a `git repack -adf` on the primary repo (i.e. the bare repo on the server) fixed that. However, the Go module proxy seems to once again have cached the fetch error, so here we go again with yet another release. Fingers crossed that this one will be picked up. + # v0.13.1 (2026-07-31) No changes to the previous version. The Go module proxy refused to pick up v0.13.0 because the tag was pushed before the `main` branch was updated. Hopefully it will pick up this release. |