-
Release v0.23.0
StableSome checks failedchangelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 4schangelog-body-check / check (pull_request) Successful in 0scheck-self-bootstrap / check (pull_request) Failing after 3sfragment-check / changelog fragment-kind (pull_request) Successful in 4sfragment-check / check (pull_request) Successful in 0smanifest-check / manifest-vs-tag consistency (pull_request) Successful in 5smanifest-check / check (pull_request) Successful in 0scheck-self-bootstrap / check (push) Failing after 4srelease / decide + act (push) Successful in 6srelease / release (push) Successful in 0sreleased this
2026-07-02 23:41:14 +02:00 | 1206 commits to main since this releasePost-v0.22.0 correctness fix: retire the release-notes sidecar so edits to
CHANGELOG.mdactually reach the Forgejo release page.Removed
BREAKING:
.release-toolkit-release-notes.mdsidecar retired — CHANGELOG.md is the single source of truth for the release-body content. The v0.5.0-introduced sidecar (fed by fragmentsummary:frontmatter) was preferred bydraft-release.shover the CHANGELOG section, so edits toCHANGELOG.mdwere silently ignored on the release page.draft-release.shnow always reads the CHANGELOG section.release-prep.shno longer writes a sidecar and deletes any legacy committed sidecar on the first post-#301 cut so the file stops shipping stale content.summary:frontmatter on fragments becomes inert (safe to leave or strip). Closes #301.Upgrade
If your repo has committed a
.release-toolkit-release-notes.mdfile from a pre-v0.23.0 cut, delete it:git rm .release-toolkit-release-notes.md && git commit -m "chore: drop retired sidecar per release-toolkit#301"draft-release.shignores the file post-v0.23.0, so leaving it in place is a no-op (not an error). Nothing else needed to upgrade.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)