Today we are releasing versions 16.2.4 for GitLab Community Edition and Enterprise Edition.
These versions resolve a number of regressions and bugs.
GitLab Community Edition and Enterprise Edition
16.2.4
- Backport '420347-fix-new-index-settings' to 16.2
- Backport Fix max number of slices to 16.2
- Put back broadcast messages to sign-in page for self-hosted
- Revert "Remove log_response_length feature flag" - 16.2 Backport
- Fix broken dependency list for invalid Container Scanning pkg mgr type
- Replace vscode-cdn.net with web-ide.gitlab-static.net (Backport)
- Set proxy_http_version v1.0 for health monitoring endpoints
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 want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.
Share your feedback