Today we are releasing version 8.6.1 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version includes many fixes and improvements.
Read on for all the details!
- EE: Only rename the
light_logocolumn in the
appearancestable if it is not there yet. (!290)
- EE: Fix diffs in text part of email-on-push messages. (!293)
- EE: Fix an issue with methods not accessible in some controllers. (!295)
- EE: Ensure
- CE/EE: Add option to reload the schema before restoring a database backup. (!2807)
- CE/EE: Display navigation controls on mobile. (!3214)
- CE/EE: Fix a bug where participants would not work correctly on merge requests. (!3329)
- CE/EE: Fix sorting issues by votes on the groups issues page results in SQL errors. (!3333)
- CE/EE: Restrict notifications for confidential issues. (!3334)
- CE/EE: Do not allow to move issue if it has not been persisted. (!3340)
- CE/EE: Add a confirmation step before deleting an issuable. (!3341)
- CE/EE: Fix an issue with the sign-in button overflowing on mobile. (!3342)
- CE/EE: Auto-collapses the navigation sidebar when resizing. (!3343)
- CE/EE: Fix build dependencies, when the dependency is a string. (!3344)
- CE/EE: Show error messages when trying to create a label in dropdown menu. (!3345)
- CE/EE: Fix an issue with assign milestone not loading milestone list. (!3346)
- CE/EE: Fix an issue causing the Dashboard > Milestones page to be blank. (!3348)
- Omnibus GitLab: Fix artifacts path key in
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
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 included with 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