diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-08-20 18:42:06 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-08-20 18:42:06 +0000 |
| commit | 6e4e1050d9dba2b7b2523fdd1768823ab85feef4 (patch) | |
| tree | 78be5963ec075d80116a932011d695dd33910b4e /doc/update/README.md | |
| parent | 1ce776de4ae122aba3f349c02c17cebeaa8ecf07 (diff) | |
| download | gitlab-ce-6e4e1050d9dba2b7b2523fdd1768823ab85feef4.tar.gz | |
Add latest changes from gitlab-org/gitlab@13-3-stable-ee
Diffstat (limited to 'doc/update/README.md')
| -rw-r--r-- | doc/update/README.md | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/doc/update/README.md b/doc/update/README.md index fa9fdee4ed4..85fc4363673 100644 --- a/doc/update/README.md +++ b/doc/update/README.md @@ -50,7 +50,8 @@ However, for this to work there are the following requirements: migrations](../development/post_deployment_migrations.md) (included in zero downtime update steps below). - You are using PostgreSQL. Starting from GitLab 12.1, MySQL is not supported. -- Multi-node GitLab instance. Single-node instances may experience brief interruptions as services restart. +- Multi-node GitLab instance. Single-node instances may experience brief interruptions + [as services restart (Puma in particular)](https://docs.gitlab.com/omnibus/update/README.html#single-node-deployment). Most of the time you can safely upgrade from a patch release to the next minor release if the patch release is not the latest. For example, upgrading from @@ -200,7 +201,7 @@ Below you can find some guides to help you change editions easily. ### Community to Enterprise Edition ->**Note:** +NOTE: **Note:** The following guides are for subscribers of the Enterprise Edition only. If you wish to upgrade your GitLab installation from Community to Enterprise @@ -221,6 +222,11 @@ possible. ## Version specific upgrading instructions +### 13.3.0 + +The recommended Git version is Git v2.28. The minimum required version of Git +v2.24 remains the same. + ### 13.2.0 GitLab installations that have multiple web nodes will need to be @@ -232,6 +238,11 @@ After upgrading, if some of your users are unexpectedly encountering 404 or 422 or "blocked" messages when using the command line, their accounts may have been un-confirmed. In that case, please ask them to check their email for a re-confirmation link. +For more information, see our discussion of [Email confirmation issues](../user/upgrade_email_bypass.md). + +GitLab 13.2.0 relies on the `btree_gist` extension for PostgreSQL. For installations with an externally managed PostgreSQL setup, please make sure to +[install the extension manually](https://www.postgresql.org/docs/11/sql-createextension.html) before upgrading GitLab if the database user for GitLab +is not a superuser. This is not necessary for installations using a GitLab managed PostgreSQL database. ### 13.1.0 |