Today we are releasing versions 17.10.3 for GitLab Community Edition and Enterprise Edition.
These versions resolve a number of regressions and bugs. This patch release does not include any security fixes.
GitLab Community Edition and Enterprise Edition
17.10.3
- CI: Use gcr mirror in DinD (17.10 Backport)
- No-op ci_runner_machines_687967fa8a batched migrations - 17.10 backport
- Ensure runner taggings are copied from taggings
- Fix free push limit on non-saas
- Backport fix in libarchive for CI
- CI: Use gcr mirror for DinD (17.10 Backport)
- [17.10 Backport] Check packages does not have .dind job in scope
Important notes on upgrading
This version includes new post deployment 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.
Note: GitLab releases have skipped 17.10.2. There is no patch with that version number.
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