Today we are releasing version 12.10.3 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 12.10 release and prior versions.
GitLab Community Edition and Enterprise Edition
Available in GitLab Core, Starter, Premium, and Ultimate:
- Disable schema dumping after migrations in production
- Fix a CI failure where no jobs can be requested by and assigned to runners based on certain instance settings
- Escape branch name on backend
- Add LFS badge feature flag to RefsController#logs_tree
- Fix second 500 error with NULL restricted visibility levels
- Fix incorrect commits number in commits list
- Fix errors creating project with active Prometheus service template
- Enable expiring license banner
- Fix CaptureDiffNotePositionService when position is nil
- Fix terraform state init failure
- Move deploy keys section back to repository settings
- Update pagination and limits documentation for projects API
Available in GitLab Premium and Ultimate:
Important notes on upgrading
This version does not include any new migrations, and 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.
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