GitLab Patch Release: 18.11.9
On August 6, 2026, we released versions 18.11.9 for GitLab Community Edition and Enterprise Edition.
These versions resolve a number of regressions and bugs. This patch release does not include any security fixes.
GitLab Community Edition and Enterprise Edition
18.11.9
We have pulled the omnibus install of 18.11.8 and replaced it with 18.11.9. A bug was found in the deprecation code that enabled Mattermost incorrectly.
If you have a local cache of our omnibus package, you will want to remove 18.11.8 and get 18.11.9.
- Update gitlab-logger to v4.0.1 (18-11-stable)
- Backport of ‘Keep virtual registry settings toggle visible when disabled’ into 18.11
- Backport of “Fix blob preview diff hiding blank added lines”
- Backport of ‘Backfill duo_secret_detection_fp_enabled to false’
- [18.11] Backport of “Remove –unlink-first and –recursive-unlink from tar extract”
- Backport of ‘Add postgres_index_bloat_estimate SQL function’
- [18.11 Backport] Bump PostgreSQL versions to 16.14 and 17.10
- Backport fix for Mattermost deprecation to 18.11
- Fix accidental enable of mattermost by deprecation check -> in 18.11.9
Important notes on upgrading
This patch includes database migrations that may impact your upgrade process.
Postgresql server versions were updated to 16.14 and 17.10 to include the latest upstream patches and fixes.
This version fixes an issue where upgrading to 19.x failed with a Mattermost deprecation error for Linux package installations, even when Mattermost was not actively configured. Upgrade to this version before upgrading to 19.0 or later. For details, see Mattermost removed from the Linux package.
On very large installations, the gitlab:db:reindex task could time out while estimating index bloat for a single index, causing the job to fail repeatedly and leaving PostgreSQL indexes to grow increasingly bloated, which in turn degraded overall instance performance and complicated upgrades. This release restructures the bloat-estimation query for single-index lookups, restoring reliable automatic reindexing on large databases.
Impact on your installation:
- Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
- Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.
Regular migrations
The following version includes regular migrations that run during the upgrade process:
- 18.11.9
Post-deploy migrations
The following version includes post-deploy migrations that can run after the upgrade:
- 18.11.9
To learn more about the impact of upgrades on your installation, see:
- Zero-downtime upgrades for multi-node deployments
- Standard upgrades for single-node installations
Updating
To update, check out our update page.
GitLab subscriptions
Access to GitLab Premium and Ultimate features is granted by a paid subscription.
Alternatively, sign up for GitLab.com to use GitLab’s own infrastructure.