Today we are releasing version 10.5.2 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 10.5 release.
GitLab Community Edition and Enterprise Edition
Available in GitLab Core, Starter, Premium, and Ultimate:
- Avoid slow File Lock checks when not used
- Only check LFS integrity for first branch in push
- Fix bug for MR stating "Could not connect to the CI server"
- Fix bug when loading an invalid upload URL
- Fix bug when checking for a repo in GitAccessWiki
- Enable "Legacy Authorization" by default when creating a Cluster on GCP
- Fix stacked progress bar bug
- Fix bug when attempting to update tracked field for read-only DB
- Fix bug to allow branchnames to be named the same as the commit it points to
- Fix bug for sidekiq metrics
- Fix issue with CI cache key being empty when variable used as the key
- Fix bug where diff errors displayed unnecessarily
- Improve query performance for
- Performance improvements when searching for Project members
- Improve performance of searching for and auto completing of users
- Performance improvements regarding feature flags
Available in GitLab Starter, Premium, and Ultimate:
Available in GitLab Premium and Ultimate:
- Fix bug where
- Geo: Support a custom database login for PostgreSQL FDW to work with pgbouncer
This version does include new migrations, but 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
which is only used for updates.
To update, check out our update page.
Access to GitLab Starter, Premium, and Ultimate features is granted by a paid subscription.
Alternatively, sign up for GitLab.com to use GitLab's own infrastructure.