diff options
Diffstat (limited to 'doc/update/index.md')
| -rw-r--r-- | doc/update/index.md | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/update/index.md b/doc/update/index.md index b821be3deea..f7e3a0e3403 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -165,7 +165,7 @@ cannot guarantee that upgrading between major versions is seamless. A *major* upgrade requires the following steps: -1. Identify a [supported upgrade path](#upgrade-paths). +1. Identify a [supported upgrade path](#upgrade-paths). The last minor release of the previous major version is always a required stop due to the background migrations being introduced in the last minor version. 1. Ensure that any [background migrations have been fully completed](background_migrations.md) before upgrading to a new major version. 1. If you have enabled the [Elasticsearch integration](../integration/advanced_search/elasticsearch.md), then @@ -193,7 +193,11 @@ When upgrading: GitLab instances with multiple web nodes) > [`15.4.6`](versions/gitlab_15_changes.md#1540) > [`15.11.13`](versions/gitlab_15_changes.md#15110). - GitLab 16: [`16.0.x`](versions/gitlab_16_changes.md#1600) (only - [instances with lots of users](versions/gitlab_16_changes.md#long-running-user-type-data-change)) > [`16.3`](versions/gitlab_16_changes.md#1630) > [latest `16.Y.Z`](https://gitlab.com/gitlab-org/gitlab/-/releases). + instances with [lots of users](versions/gitlab_16_changes.md#long-running-user-type-data-change) or + [large pipeline variables history](versions/gitlab_16_changes.md#1610)) > + [`16.1`](versions/gitlab_16_changes.md#1610)(instances with NPM packages in their Package Registry) > + [`16.2.x`](versions/gitlab_16_changes.md#1620) (only instances with [large pipeline variables history](versions/gitlab_16_changes.md#1630)) > + [`16.3`](versions/gitlab_16_changes.md#1630) > [latest `16.Y.Z`](https://gitlab.com/gitlab-org/gitlab/-/releases). 1. Check for [required upgrade stops](#required-upgrade-stops). 1. Consult the [version-specific upgrade instructions](#version-specific-upgrading-instructions). @@ -214,7 +218,7 @@ upgrade stops allow required background migrations to finish. During GitLab 16.x, we are scheduling required upgrade stops beforehand so users can better plan out appropriate upgrade stops and downtime when necessary. -The first scheduled required upgrade stop has been announced for 16.3. When planning upgrades, please take this into account. +The first scheduled required upgrade stop has been announced for 16.3.x. When planning upgrades, please take this into account. ### Earlier GitLab versions |