1.17.1 released

master
Loïc Dachary 2022-08-19 07:20:47 +10:00
parent ab01e4ad05
commit 497f952341
Signed by: dachary
GPG Key ID: 992D23B392F9E4F2
1 changed files with 7 additions and 7 deletions

View File

@ -30,9 +30,9 @@ It is **critical** to verify that Gitea works very carefully. Restoring the back
* Manually analyze (reading the patches to the sources of the template directory) and update the [customized CSS / content](https://docs.gitea.io/en-us/upgrade-from-gitea/#take-care-about-customized-templates).
* [Do not use `gitea help`](https://discourse.gitea.io/t/gitea-custom-themes-not-working/4040/7) to figure out the location of `CustomPath`, look at the configuration tab of the administration panel when logged in as an admin.
* `gitea manager flush-queues`. If it timesout, run it again with a more generous `--timeout` argument. It is important because the queues contain serialized data that is not guaranteed to be backward compatible between versions. See [this breaking change example](https://blog.gitea.io/2022/03/gitea-1.16.4-is-released/#breaking-change-refactor-mirror-code--fix-starttomirror-19075httpsgithubcomgo-giteagiteapull19075) to better understand why this is necessary.
* With [Gitea version >=1.17](https://github.com/go-gitea/gitea/pull/15928)
* With [Gitea version >=1.17.1](https://github.com/go-gitea/gitea/pull/15928)
* go to the web admin panel and pause all queues
* With Gitea version < 1.17
* With Gitea version < 1.17.1
* Shutdown Gitea so that no new entry is created in the queues
---
@ -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.17.0 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.1 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.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).
* Upgrade to 1.17.1 (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
@ -68,7 +68,7 @@ The database version is stored in the database and can be retrieved with **selec
| Gitea version | Date | Database |
| --------------| ---- | ---------------- |
|[1.17.0](https://github.com/go-gitea/gitea/releases/tag/v1.17.0) | July 2022 | v224 |
|[1.17.1](https://github.com/go-gitea/gitea/releases/tag/v1.17.1) | July 2022 | v224 |
|[1.16.9](https://github.com/go-gitea/gitea/releases/tag/v1.16.9) | July 2022 | v211 |
|[1.15.11](https://github.com/go-gitea/gitea/releases/tag/v1.15.11) | January 2022| v189 |
|[1.14.7](https://github.com/go-gitea/gitea/releases/tag/v1.14.7) | September 2021| v178 |
@ -80,7 +80,7 @@ The database version is stored in the database and can be retrieved with **selec
### When upgrading from a specific version...
* Any version before [1.17](https://github.com/go-gitea/gitea/releases/tag/v1.17.0-rc2)
* Any version before [1.17](https://github.com/go-gitea/gitea/releases/tag/v1.17.1)
* preserve a custom gitconfig: [episode 1](https://hostea.org/blog/1-17-breaking-episode-1/), [episode 2](https://hostea.org/blog/1-17-breaking-episode-2/)
* [1.13.0](https://blog.gitea.io/2020/12/gitea-1.13.0-is-released/)
* The Webhook shared secret inside the webhook payload has been deprecated and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755 please use the secret header that uses an hmac signature to validate the webhook payload.
@ -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.17.0 or greater](https://github.com/go-gitea/gitea/pull/19656) and run `gitea doctor --all --fix`
* Workaround: upgrade to [1.17.1 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)