summaryrefslogtreecommitdiffstats
path: root/RELEASE-NOTES.md
diff options
context:
space:
mode:
authorEarl Warren <contact@earl-warren.org>2024-04-24 08:36:24 +0200
committerEarl Warren <contact@earl-warren.org>2024-04-24 08:36:24 +0200
commita7602781c494bc7061f0e7d31f2dd82b3adc9504 (patch)
treef7c4ac74b0d4f076fefbad9ca3d894d475f3f9e5 /RELEASE-NOTES.md
parentMerge pull request 'fix(docs): v7.0.0 admin user create regression' (#3404) f... (diff)
downloadforgejo-a7602781c494bc7061f0e7d31f2dd82b3adc9504.tar.xz
forgejo-a7602781c494bc7061f0e7d31f2dd82b3adc9504.zip
feat(docs): 7.0.1 release notes template
so that individual commits can include additions to the release notes when relevant.
Diffstat (limited to 'RELEASE-NOTES.md')
-rw-r--r--RELEASE-NOTES.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md
index 1574a403ca..9a1c19632d 100644
--- a/RELEASE-NOTES.md
+++ b/RELEASE-NOTES.md
@@ -4,6 +4,14 @@ 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.
+## 7.0.1
+
+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 following notable bug fixes, you can browse the [full list of commits](https://codeberg.org/forgejo/forgejo/compare/v7.0.0...v7.0.1) included in this release.
+
+* **Bug fixes:**
+
## 7.0.0
The [complete list of commits](https://codeberg.org/forgejo/forgejo/commits/branch/v7.0/forgejo) included in the `Forgejo v7.0.0` release can be reviewed from the command line with: