GitLab Patch Release: 18.9.8, 18.8.10, 18.7.7, 18.6.8, 18.5.7
Today, we are releasing versions 18.9.8, 18.8.10, 18.7.7, 18.6.8, and 18.5.7 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.
This patch release addresses a regression introduced in GitLab 18.4 where issues appeared duplicated in Epic swimlane board views — showing under both their direct parent epic and the grandparent epic — even when no filter was applied. This caused boards to become cluttered and made iteration planning unreliable for teams using nested epic hierarchies. The fix restores the intended behavior: issues appear only under their direct parent epic in unfiltered swimlane views, while the full hierarchy is still shown when a user explicitly filters by a specific parent epic. Customers affected by this issue are encouraged to upgrade to the patched version.
GitLab Community Edition and Enterprise Edition
18.9.8
- Backport of
Fix swimlane problem - Backport of Fix flaky new_project_spec CI/CD from repo URL test to 18-9
- Backport ‘Pass down DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-9-stable-ee
- Backport ‘Bump nginx to version 1.30.1’ to 18-9
- [18.9] Mattermost Security Updates May 13, 2026
18.8.10
- [18.8] Scope start-rails-specs changes rule to MR pipelines
- 18.8 Backport of ‘update zlib to 3.2.3’
- [Backport 18.8]Fix PG::UniqueViolation in project_daily_statistics sync trigger
- Docs backport: Add note about Agent Platform flow configurations not available until 18.11
- Backport of
Fix swimlane problem - Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-8-stable-ee
- 18.8 backport of ‘Update rack to 2.2.23’
- Backport: fix: Set sv timeout when restarting Gitaly to 18.8
- [18.8] Remove Mattermost for SLES-12.5
18.7.7
- [18.7] Update dependency oj to v3.16.15
- [18.7] GLQL advanced finder, remove project_ids
- Backport
ojandoj-introspectgem updates - Backport “CI: Update CNG mirror skip job regex”
- Backport of
Fix swimlane problem - Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-7-stable-ee
- 18.7 Backport CI: Fix the package install for zypper based distros
- [18.7] Backport Mattermost Security Updates February 23, 2026
- Backport 18-7-stable - check-packages uses Pulp
18.6.8
- Backport of Validate milestone title for group import
- Backport of ‘Remove unused retag-gdk-image CI job’
- Backport: Quarantine flaky github oauth spec
- Backport of
Fix swimlane problem - Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-6-stable-ee
- Backport Pulp migration changes to 18.6
18.5.7
- 18.5 Backport: “Add type handling for findings with locations saved as Strings”
- Backport of Fix content and content-type mismatch in files e2e test
- [Backport 18.5] Exclude Git HTTP requests from authenticated web throttle
- Backport of: Handle updated Jira API calls to permit Jira issue imports again
- Backport(18.5): Update dependency @gitlab/web-ide to ^0.0.1-dev-20251210140521
- Backport of ‘Workhorse: use upstream for DWS API requests’
- Backport of flaky import spec quarantine
- Backport of “Removes feature flag enablement for svc accounts”
- Backport 18.5 - Fix searchable dropdown race condition when typing fast
- Backport: Properly quarantine broken ci spec
- Backport of
Fix swimlane problem - Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-5-stable-ee
- 18.5 - Remove manual from SLES-12.5-release-pulp job
- Start Pulp FIPS jobs after PC FIPS jobs - 18.5
- Backport Pulp migration changes to 18.5
Important notes on upgrading
This patch includes database migrations that may impact your upgrade process.
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.
Post-deploy migrations
The following version includes post-deploy migrations that can run after the upgrade:
- 18.8.10
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
Note: GitLab releases have skipped 18.6.7 and 18.5.6. There are no patches with these version numbers.
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.