Add a notice for breaking check in upgrade document (#20682)
This commit is contained in:
parent
42d9a6a980
commit
8a66967020
1 changed files with 6 additions and 0 deletions
|
@ -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.
|
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.
|
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
|
## Backup for downgrade
|
||||||
|
|
||||||
Gitea keeps compatibility for patch versions whose first two fields are the same (`a.b.x` -> `a.b.y`),
|
Gitea keeps compatibility for patch versions whose first two fields are the same (`a.b.x` -> `a.b.y`),
|
||||||
|
|
Loading…
Reference in a new issue