GitLab Patch Release: 17.0.7

Today we are releasing versions 17.0.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 Community Edition and Enterprise Edition

17.0.7

• Backport 17.0: Release Environments - pipeline level resource group
• Backport 17.0: Build assets image when running release environments
• Backport 17.0 - Do not run release-environments on tagging
• Backport canonical RE downstream pipeline removal
• Update minimum Go version requirement for self-compiled (17.0)
• Backport 17.0: Always build assets image when tagging
• Backport gitlab-qa shm fix 17.0
• CI: Add test basic package functionality before release (17.0 Backport)
• Use latest builder images for check-packages pipeline (17.0 Backport)
• [17.0 Backport] Deprecate CentOS 7
• Backport to 17.0: Fix JobArtifactState query timeout

Important notes on upgrading

This version does not include any new migrations, and for multi-node deployments, should not require any downtime.

Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates.

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.

We’re combining patch and security releases

This improvement in our release process matches the industry standard and will help GitLab users get information about security and bug fixes sooner, read the blog post here.