Today we are releasing version 10.1.1 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version resolves a number of regressions and bugs in the 10.1.0 release and prior versions.
It includes the following fixes:
- CE/EE: Auto Devops Kubernetes default namespace is now correctly built out of GitLab (!14642)
- CE/EE: Store circuitbreaker settings in the database instead of config (!14842)
- CE/EE: Allow boards as top level route (!14861)
- CE/EE: Forbid the usage of
- CE/EE: Make the circuitbreaker more robust by adding higher thresholds, and multiple access attempts. (!14933)
- CE/EE: Update default disabled merge request widget message to reflect a general failure (!14960)
- CE/EE: Only cache last push event for existing projects when pushing to a fork (!14989)
- CE/EE: Fix deletion of container registry or images returning an error (!14992)
- CE/EE: Fix the writing of invalid environment refs (!14993)
- CE/EE: Fix bug preventing secondary emails from being confirmed (!15010)
- CE/EE: Fix broken wiki pages that link to a wiki file (!15019)
- CE/EE: Don't rename paths that were freed up when upgrading (!15029)
- CE/EE: Fix editing issue description in mobile view (!15049)
- CE/EE: Fix Bitbucket login (!15051)
- CE/EE: Update Gitaly in GitLab 10.1 to 0.43.1 for temp file cleanup (!15055)
- CE/EE: Stop merge requests with thousands of commits from timing out (!15063)
- CE/EE: Use the correct visibility attribute for projects in system hooks (!15065)
- CE/EE: Fix widget of locked merge requests not being presented (!15069)
- CE/EE: Normalize LDAP DN when looking up identity (!15103)
- CE/EE: Add callback functions for initial request in clusters page (!15105)
- CE/EE: Fix missing Import/Export issue assignees (!15109)
- EE: Move group boards routes under - and remove "boards" from reserved paths (!3078)
- EE: Fix height of rebase and approve buttons (!3210)
- EE: Fix LDAP group sync for nested groups e.g. when base has uppercase or extraneous spaces (!3217)
- EE: Geo: read-only safeguards was not working on Secondary node (!3227)
This version includes two migrations and no downtime would be required.
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
To update, check out our update page.
Interested in GitLab Enterprise Edition? Check out the features exclusive to EE.
Access to GitLab Enterprise Edition 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