@@ -314,7 +314,7 @@ Git 2.33.x and later is required. We recommend you use the
...
@@ -314,7 +314,7 @@ Git 2.33.x and later is required. We recommend you use the
### 14.3.0
### 14.3.0
Ruby 2.7.4 is required. Refer to [the Ruby installation instructions](../install/installation.md#2-ruby)
-Ruby 2.7.4 is required. Refer to [the Ruby installation instructions](../install/installation.md#2-ruby)
for how to proceed.
for how to proceed.
- GitLab 14.3.0 contains post-deployment migrations to [address Primary Key overflow risk for tables with an integer PK](https://gitlab.com/groups/gitlab-org/-/epics/4785) for the tables listed below:
- GitLab 14.3.0 contains post-deployment migrations to [address Primary Key overflow risk for tables with an integer PK](https://gitlab.com/groups/gitlab-org/-/epics/4785) for the tables listed below:
...
@@ -366,25 +366,25 @@ for how to proceed.
...
@@ -366,25 +366,25 @@ for how to proceed.
### 14.1.0
### 14.1.0
-Due to an issue where `BatchedBackgroundMigrationWorkers` were
Due to an issue where `BatchedBackgroundMigrationWorkers` were
for self-managed instances, a [fix was created](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65106)
for self-managed instances, a [fix was created](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65106)
and a [14.0.Z](#1400) version was released. If you haven't updated to 14.0.5, you need
and a [14.0.Z](#1400) version was released. If you haven't updated to 14.0.5, you need
to update to at least 14.1.0 that contains the same fix before you update to
to update to at least 14.1.0 that contains the same fix before you update to
a later version.
a later version.
After you update to 14.1.0,
After you update to 14.1.0,
[batched background migrations need to finish](../user/admin_area/monitoring/background_migrations.md#check-the-status-of-background-migrations)
[batched background migrations need to finish](../user/admin_area/monitoring/background_migrations.md#check-the-status-of-background-migrations)
before you update to a later version.
before you update to a later version.
If the migrations are not finished and you try to update to a later version,
If the migrations are not finished and you try to update to a later version,
you'll see an error like:
you'll see an error like:
```plaintext
```plaintext
Expected batched background migration for the given configuration to be marked as 'finished', but it is 'active':
Expected batched background migration for the given configuration to be marked as 'finished', but it is 'active':
```
```
See how to [resolve this error](../user/admin_area/monitoring/background_migrations.md#database-migrations-failing-because-of-batched-background-migration-not-finished).
See how to [resolve this error](../user/admin_area/monitoring/background_migrations.md#database-migrations-failing-because-of-batched-background-migration-not-finished).