Today we are releasing version 10.8.3 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 10.8 release and prior versions.
GitLab Community Edition and Enterprise Edition
Available in GitLab Core, Starter, Premium, and Ultimate:
- Optimize database version method
- Adds migration to ensure all remote mirror columns get created
- Upgrade workhorse to v4.2.1
- Bump rugged to 0.27.1 for security fixes
- Fix local storage not being cleared after creating a new issue
- Fix encoding of branch names on compare and new merge request page
- Fix assumption of GitLab installation as a git working copy
- Upgrades Gitaly to 0.100.1
Available in GitLab Premium and Ultimate:
- Geo: Fixes repository verification getting stuck when all projects have been verified at least once
- Geo: Make
Geo::PruneEventLogWorkerdelete rows more gently
This version includes a new migration that should not require any downtime. This migration should only affect users who went from EE to CE and had issues upgrading to
10.8.2. GitLab.com migrations took approximately 0 minutes.
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-migrations file, 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.
Alternativelly, sign up for GitLab.com to use GitLab's own infrastructure.