summaryrefslogtreecommitdiffstats
path: root/docs/content
diff options
context:
space:
mode:
authorwxiaoguang <wxiaoguang@gmail.com>2022-08-05 22:20:13 +0800
committerGitHub <noreply@github.com>2022-08-05 10:20:13 -0400
commit8a669670206d67a9e9d8229040662f4e14078385 (patch)
treef46836b6044fd8dda562deeffc873dd0778b5aa5 /docs/content
parent42d9a6a980beab35311a7242b4d4c7f2736c64a0 (diff)
downloadgitea-8a669670206d67a9e9d8229040662f4e14078385.tar.gz
gitea-8a669670206d67a9e9d8229040662f4e14078385.zip
Add a notice for breaking check in upgrade document (#20682)
Diffstat (limited to 'docs/content')
-rw-r--r--docs/content/doc/upgrade/from-gitea.en-us.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/content/doc/upgrade/from-gitea.en-us.md b/docs/content/doc/upgrade/from-gitea.en-us.md
index f5c9551f31..0d22a32439 100644
--- a/docs/content/doc/upgrade/from-gitea.en-us.md
+++ b/docs/content/doc/upgrade/from-gitea.en-us.md
@@ -23,6 +23,12 @@ To update Gitea, download a newer version, stop the old one, perform a backup, a
Every time a Gitea instance starts up, it checks whether a database migration should be run.
If a database migration is required, Gitea will take some time to complete the upgrade and then serve.
+## Check the Changelog for breaking changes
+
+To make Gitea better, some breaking changes are unavoidable, especially for big milestone releases.
+Before upgrade, please read the [Changelog on Gitea blog](https://blog.gitea.io/)
+and check whether the breaking changes affect your Gitea instance.
+
## Backup for downgrade
Gitea keeps compatibility for patch versions whose first two fields are the same (`a.b.x` -> `a.b.y`),