Today we are releasing version 10.3.1 for GitLab Community Edition (CE) and Enterprise Editions (EES, EEP).
This version resolves a number of regressions and bugs in this month's 10.3.0 release and prior versions.
Bug fixes for Community and Enterprise Editions
- CE/EES/EEP: Fix Error 500s with anonymous clones for a project that has moved.
- CE/EES/EEP: Don't link LFS-objects multiple times.
- CE/EES/EEP: Reduce cardinality of some of GitLab's Prometheus metrics and fix observed duration reporting.
- CE/EES/EEP: Execute project hooks and services after commit when moving an issue.
- CE/EES/EEP: Fix cluster environment missing.
- CE/EES/EEP: Use Concurrent::AtomicReference instead AtomicFixnum
Bug fixes for Enterprise Editions
Bug fixes for Omnibus GitLab
- Make it possible to configure an external Geo tracking database.
- Process reconfigure failures and print out a message.
- Remove unused redis bin gitlab-shell configuration.
- Bump bundled git version to 2.14.3 a2b4bedf.
- Update pgbouncer recipe to better handle initial configuration.
- Render gitaly-ruby memory settings.
- Add a runit service to probe repository storages.
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.
Interested in GitLab Enterprise Editions? Check out the features exclusive to EE.
Access to GitLab Enterprise Editions is granted by a subscription. No time to upgrade GitLab yourself? Subscribers receive upgrade and installation services.
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