diff options
author | Earl Warren <contact@earl-warren.org> | 2024-08-09 07:26:50 +0200 |
---|---|---|
committer | Earl Warren <contact@earl-warren.org> | 2024-08-09 07:26:50 +0200 |
commit | b87b38d3b9bbf90d69fdfd3fe32178f6c5937ff2 (patch) | |
tree | c109c804774337723893a14c66f41e89b1997de8 | |
parent | Merge pull request 'feat(performance): remove `BranchName` in `/:owner/:repo/... (diff) | |
download | forgejo-b87b38d3b9bbf90d69fdfd3fe32178f6c5937ff2.tar.xz forgejo-b87b38d3b9bbf90d69fdfd3fe32178f6c5937ff2.zip |
docs: add links to the v7.0.7 & v8.0.1 release notes
They are now published in the milestone in part manually edited and in
part generated by the release notes assistant. Maintaining a single
file with all the release notes is prone to conflicts and requires
manual copy/pasting that is of little value.
It may make sense to transition to a release notes directory in which
the release notes assistant could create one file per release, with a
copy of the release notes edited in the milestone. This could be more
conveniently backported and would not require human intervention.
-rw-r--r-- | RELEASE-NOTES.md | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md index 5d37d5a75d..2e0eec1dc0 100644 --- a/RELEASE-NOTES.md +++ b/RELEASE-NOTES.md @@ -4,9 +4,11 @@ A minor or major Forgejo release is published every [three months](https://forge A [patch or minor release](https://semver.org/spec/v2.0.0.html) (e.g. upgrading from v7.0.0 to v7.0.1 or v7.1.0) does not require manual intervention. But [major releases](https://semver.org/spec/v2.0.0.html#spec-item-8) where the first version number changes (e.g. upgrading from v1.21 to v7.0) contain breaking changes and the release notes explain how to deal with them. -## Upcoming releases (not available yet) +The release notes of each release [are available in the corresponding milestone](https://codeberg.org/forgejo/forgejo/milestones), starting with [Forgejo 7.0.7](https://codeberg.org/forgejo/forgejo/milestone/7683) and [Forgejo 8.0.1](https://codeberg.org/forgejo/forgejo/milestone/7682). -- [9.0.0](release-notes/9.0.0/) +## 8.0.1 + +The Forgejo v8.0.1 release notes are [available in the v8.0.1 milestone](https://codeberg.org/forgejo/forgejo/milestone/7682). ## 8.0.0 @@ -145,6 +147,10 @@ A [companion blog post](https://forgejo.org/2024-07-release-v8-0/) provides addi - [PR](https://codeberg.org/forgejo/forgejo/pulls/2937): <!--number 2937 --><!--number--><!--description -->31 March updates<!--description--> <!--end release-notes-assistant--> +## 7.0.7 + +The Forgejo v7.0.7 release notes are [available in the v7.0.7 milestone](https://codeberg.org/forgejo/forgejo/milestone/7683). + ## 7.0.6 This is a bug fix release. See the documentation for more information on the [upgrade procedure](https://forgejo.org/docs/v7.0/admin/upgrade/). In addition to the pull requests listed below, you will find a complete list in the [v7.0.6 milestone](https://codeberg.org/forgejo/forgejo/milestone/7252). |