update examples now that 1.17 is released

Signed-off-by: Loïc Dachary <loic@dachary.org>
master
Loïc Dachary 2022-07-31 11:29:03 +02:00
parent b4d3bec53a
commit 09bdc0d476
Signed by: dachary
GPG Key ID: 992D23B392F9E4F2
1 changed files with 4 additions and 4 deletions

View File

@ -57,10 +57,10 @@ It is **critical** to verify that Gitea works very carefully. Restoring the back
#### Troubleshoot
* [Increase the log level](https://docs.gitea.io/en-us/logging-configuration/#debugging-problems). If the Gitea version is recent they can be modified dynamically with `gitea manager logging add console -n traceconsole -l TRACE -e '((modules/git)|(services/mirror))'`
* If the upgrade from version x.y to version x.y+2 fails and there is a need to narrow down the problem, try upgrading to the latest minor version of each major version and verify it works. It will show which major version causes the issue and help debug the problem. For instance, if upgrading from 1.14.5 to 1.16.9 does not work:
* If the upgrade from version x.y to version x.y+2 fails and there is a need to narrow down the problem, try upgrading to the latest minor version of each major version and verify it works. It will show which major version causes the issue and help debug the problem. For instance, if upgrading from 1.14.5 to 1.17.0 does not work:
* Upgrade from 1.14.5 to 1.14.6 (the last minor version of the 1.14 major version) and [verify Gitea works](#verify-gitea-works-2).
* Upgrade to 1.15.11 (the last minor version of the 1.15 major version) and [verify Gitea works](#verify-gitea-works-2).
* Upgrade to 1.16.9 (the last minor version of the 1.16 major version at this point in time) and [verify Gitea works](#verify-gitea-works-2).
* Upgrade to 1.17.0 (the last minor version of the 1.17 major version at this point in time) and [verify Gitea works](#verify-gitea-works-2).
### List of latest major versions
@ -102,7 +102,7 @@ In your config, you can check the [security](https://docs.gitea.io/en-us/config-
* All versions
* Symptom: [blank / 500 page after login when running SQLite](https://github.com/go-gitea/gitea/issues/18650)
* Workaround: upgrade to [1.16.9 or greater](https://github.com/go-gitea/gitea/pull/19656) and run `gitea doctor --all --fix`
* Workaround: upgrade to [1.17.0 or greater](https://github.com/go-gitea/gitea/pull/19656) and run `gitea doctor --all --fix`
* [1.12.x to 1.16.x](https://discourse.gitea.io/t/fixing-broken-avatar-icons-after-upgrade/4909)
* Workaround: [manually delete broken avatars](https://discourse.gitea.io/t/fixing-broken-avatar-icons-after-upgrade/4909/2)
@ -112,7 +112,7 @@ In your config, you can check the [security](https://docs.gitea.io/en-us/config-
### Versions with known issues
Gogs from before September 2015 migrated to Gitea 1.16 may have a [dangling `pull_repo` table](https://forum.hostea.org/t/gitea-upgrade-from-gogs-to-1-16-8-unmigrated-pull-repo-table/73) and the corresponding pull requests will be removed by `gitea doctor --fix --all`.
Gogs from before September 2015 migrated to Gitea 1.17 may have a [dangling `pull_repo` table](https://forum.hostea.org/t/gitea-upgrade-from-gogs-to-1-16-8-unmigrated-pull-repo-table/73) and the corresponding pull requests will be removed by `gitea doctor --fix --all`.
[From the 1.11.3 release notes](https://blog.gitea.io/2020/03/gitea-1.11.3-and-1.10.6-released/):