# GitLab GitLab Patch Release: 18.11.2, 18.10.5

- Product: GitLab (https://whatsnew.fyi/product/gitlab)
- Vendor: GitLab
- Date: 2026-04-29
- Original notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-11-2-released/
- Permalink: https://whatsnew.fyi/product/gitlab/releases/2026-04-29-gitlab-patch-release-18.11.2-18.10.5

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

On April 29, 2026, we released versions 18.11.2 and 18.10.5 for GitLab Community Edition and Enterprise Edition. These out-of-band patch releases fix an observability gap to ensure we continue to meet…

- **added** — Add Code Suggestion to the DAP supported features for self-hosted models
- **fixed** — Clear persisted filters when loading /work_items page
- **fixed** — Allow Duo Core user to still use DAP code review
- **fixed** — Add GraphQL mutation to retry failed reassignments
- **fixed** — Resolve sidekiq spikes when a User is banned
- **fixed** — Fix MCP OAuth discovery failing on relative URL installs
- **added** — Add *_oldest_unsynced_time metric
- **changed** — Update Duo CLI version for remote flows
- **fixed** — Skip 3 migrations referencing dropped tables
- **fixed** — Fix self-hosted feature setting missing model_definitions
- **fixed** — Skip CreateOrUpdateDefaultTrackedContextWorker on Geo secondaries

Help us learn about your current experience with the documentation. Take the survey.
#### GitLab Patch Release: 18.11.2, 18.10.5
On April 29, 2026, we released versions 18.11.2 and 18.10.5 for GitLab Community Edition and Enterprise Edition.
These out-of-band patch releases fix an observability gap to ensure we continue to meet our disaster recovery RTO/RPO commitments for our GitLab Dedicated customers.
These versions also resolve a number of regressions and bugs. This patch release does not include any security fixes.
##### GitLab Community Edition and Enterprise Edition
###### 18.11.2
- Revert “Merge branch ‘ia-refactor-role-permission-enablement’ into ‘master’”
- ‘Add Code Suggestion to the DAP supported features for self-hosted models’
- ‘Clear persisted filters when loading /work_items page’
- ‘Allow Duo Core user to still use DAP code review’
- ‘GraphQL mutation to retry failed reassigments’ into 18.11
- “Resolve sidekiq spikes when a User is banned”
- Fix MCP OAuth discovery failing on relative URL installs
- ’*_oldest_unsynced_time’ metric addition
###### 18.10.5
- ‘Add Code Suggestion to the DAP supported features for self-hosted models’
- “Update Duo CLI version for remote flows”
- “BBM - Skip 3 migrations referencing dropped tables”
- ‘Allow Duo Core user to still use DAP code review’
- “Resolve sidekiq spikes when a User is banned”
- ‘Fix: self-hosted feature setting missing model_definitions’
- “fix: Skip CreateOrUpdateDefaultTrackedContextWorker on Geo secondaries”
- ’*_oldest_unsynced_time’ metric addition
##### 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.
###### Regular migrations
The following version includes regular migrations that run during the upgrade process:
- 18.10.5
###### Post-deploy migrations
The following version includes post-deploy migrations that can run after the upgrade:
- 18.11.2
- 18.10.5
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.