third_party
/
gitea
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add a notice for breaking check in upgrade document (#20682)

Browse Source
tokarchuk/v1.18
wxiaoguang 2 years ago committed by GitHub
parent 42d9a6a980
commit 8a66967020
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 6
      docs/content/doc/upgrade/from-gitea.en-us.md

6
docs/content/doc/upgrade/from-gitea.en-us.md
Unescape View File

@ -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`),

Write Preview
Loading…
Cancel
Save