GitLab Patch Release: 18.11.2, 18.10.5 | GitLab Docs

GitLab released patch versions 18.11.2 and 18.10.5 on April 29, 2026, for Community and Enterprise Editions. The releases address an observability gap affecting disaster recovery RTO/RPO commitments for GitLab Dedicated and fix several regressions and bugs. No security fixes are included.

Changes in GitLab 18.11.2

• Reverts the ia-refactor-role-permission-enablement merge.
• Adds Code Suggestions to DAP-supported features for self-hosted models.
• Preserves DAP code review access for Duo Core users.
• Clears persisted filters when loading the /work_items page.
• Adds a GraphQL mutation for retrying failed reassignment operations.
• Resolves Sidekiq spikes when users are banned.
• Fixes MCP OAuth discovery for installations using relative URLs.
• Adds the *_oldest_unsynced_time metric.
• Includes additional changes related to disaster recovery observability.

Changes in GitLab 18.10.5

• Adds Code Suggestions support for self-hosted models through DAP.
• Updates the Duo CLI version used for remote flows.
• Skips three migrations that reference dropped tables.
• Preserves DAP code review access for Duo Core users.
• Resolves Sidekiq spikes caused when users are banned.
• Fixes missing model_definitions in self-hosted feature settings.
• Prevents CreateOrUpdateDefaultTrackedContextWorker from running on Geo secondaries.
• Adds the *_oldest_unsynced_time metric.

Upgrade and migration impact

• Single-node installations: Expect downtime because migrations must finish before GitLab starts.
• Multi-node installations: Zero-downtime procedures can allow upgrades without downtime.
• Regular migrations: Included in version 18.10.5.
• Post-deploy migrations: Included in both 18.11.2 and 18.10.5.

Administrators should follow GitLab’s standard upgrade guidance for single-node systems and zero-downtime procedures for multi-node deployments before updating.