GitLab 17.11.7 Patch Release: Bug Fixes, No Security Updates

What Happened

On August 15 2025 GitLab released version 17.11.7 for Community Edition and Enterprise Edition. The update fixes regressions and bugs but contains no security fixes.

Impact

The patch backports several changes: it replaces the test-on-gdk flag with test-on-cng in backport merge‑request pipelines, quarantines failing DORA Metrics dashboard tests, ensures the docs hugo_build CI job uses the stable docs-gitlab-com branches, clears cache to avoid upgrade failures, and updates the container‑registry dependency to v4.19.2-gitlab. No new database migrations are included, so multi‑node deployments should not require downtime.

What to Do

• Plan and execute an upgrade to 17.11.7, verifying backups beforehand.
• Monitor CI pipelines for the new test-on-cng flag and the updated docs hugo_build job.
• Confirm the container‑registry component is at v4.19.2-gitlab.
• If you want to prevent the Omnibus package from automatically reconfiguring during the upgrade, create the file /etc/gitlab/skip-auto-reconfigure.
• Review the upgrade notes; the absence of migrations means no schema changes are expected.

Additional Notes

Omnibus packages stop, run migrations, and start again by default, regardless of upgrade size. This behavior can be overridden with /etc/gitlab/skip-auto-reconfigure. Because no security fixes are included, there is no immediate risk mitigation required.