From 154ee5bc9c8a91980db646ce6f17da55445a111c Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Mon, 3 Jul 2023 14:16:17 +0200 Subject: [PATCH] [DOCS] RELEASE-NOTES: 1.20.0 (squash) Woodpecker CI archive repository --- RELEASE-NOTES.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md index 71d1a99106..92a2061d6d 100644 --- a/RELEASE-NOTES.md +++ b/RELEASE-NOTES.md @@ -16,7 +16,8 @@ $ git -C forgejo log --oneline --no-merges origin/v1.19/forgejo..origin/v1.20/fo - **[Forgejo Semantic Version](https://forgejo.org/docs/v1.20/user/semver/):** The semantic version was updated to `5.0.0+0-gitea-1.20.0` because it contains breaking changes. - **Continuous Integration:** - Forgejo Actions workflows are [now available](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows) to run tests and publish releases for `Forgejo` itself. + - [Forgejo Actions](https://forgejo.org/docs/v1.20/user/actions/) workflows are [now available](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows) to run tests and publish releases for `Forgejo` itself. + - The Woodpecker CI configuration for PR verification and building releases is no longer maintained as part of Forgejo itself and was moved to its [own repository](https://codeberg.org/forgejo-contrib/forgejo-ci-woodpecker). - **Moderation:** Blocking another user is desirable if they are acting maliciously or are spamming your repository. When you block a user, Forgejo does not explicitly notify them, but they may learn through an interaction with you that is blocked. [Read more about blocking users](https://forgejo.org/docs/v1.20/user/blocking-user/). - **Package:**