Today we release GitLab 7.6.1 CE and 7.6.2 EE.
This release fixes a problem with the LDAP migrations and MySQL when upgrading. If you've already upgraded to GitLab 7.6 without problems, there is no need to upgrade to 7.6.1 CE or 7.6.2 EE.
If you've experienced a failed migration you can run this release to correct it.
If it exists you will have to manually remove the identities database table before upgrading.
Upgrading
Omnibus-gitlab packages for GitLab 7.6.1 (including GitLab CI 5.3.0) are now available.
To upgrade a GitLab installation from source please use the upgrader or the patch update guide.
To upgrade a GitLab CI installation from source, please use the upgrade guide.
Enterprise Edition
Note: we skipped GitLab EE 7.6.1. If you've upgraded to 7.6.0 EE without issues, there is no need to update to 7.6.2 EE.
Omnibus packages for GitLab Enterprise Edition 7.6.2 are available for subscribers here. For installations from source, use this guide.
Interested in GitLab Enterprise Edition? For an overview of feature exclusive to GitLab Enterprise Edition please have a look at the features exclusive to GitLab EE.
Access to GitLab Enterprise Edition is included with a subscription. No time to upgrade GitLab yourself? A subscription also entitles to our 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