GitLab Patch Release: 19.5.5, 19.4.7

On November 12, 2026, we released versions 19.5.5, 19.4.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. GitLab Orbit is now available in GitLab 19.4 and 19.5 Due to popular demand, this patch release brings GitLab Orbit to GitLab 19.4 and 19.5, so you can start using Orbit without upgrading to 19.6 first. Patch releases normally contain only bug and security fixes. Adding Orbit is a one-time exception, so it ships on its own in this out-of-band patch release. Orbit is off by default, so nothing changes for instances that don’t turn it on. To use Orbit, install it as a separate service on Kubernetes, turn it on in your GitLab configuration, and then turn it on for each top-level group. For details, see Set up GitLab Orbit. If you turn on Orbit on GitLab 19.4.7 and then later upgrade to 19.5, upgrade to 19.5.5 or later. Earlier 19.5 releases do not include these Orbit changes. Later patch releases for 19.4 and 19.5, including security releases, also include them. GitLab Community Edition and Enterprise Edition 19.5.5 Backport of ‘Retry GCS default credentials after a latched metadata timeout’ Backport of ‘Skip code navigation lookups when a project has no LSIF artifacts’ into 19.5 [19.5] Backport of ‘Update oj to 3.17.8 to fix native memory-safety bugs’ Backport of ‘Stop relation batch export spec leaking a foo directory’ Backport of ‘Map sast_iac scanner to sast in approval policy rules’ Backport of ‘Bump premailer to 1.27.0 to stop css_parser deprecation warnings’ (19.5) [19.5] Reapply the Orbit feature backports 19.4.7 Backport of ‘Skip code navigation lookups when a project has no LSIF artifacts’ into 19.4 Backport of ‘Retry GCS default credentials after a latched metadata timeout’ [19.4] Backport of ‘Update oj to 3.17.8 to fix native memory-safety bugs’ Backport of ‘Map sast_iac scanner to sast in approval…