Today we are releasing version 11.0.2 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 11.0 release and prior versions.
GitLab Community Edition and Enterprise Edition
Available in GitLab Core, Starter, Premium, and Ultimate:
- Adds feature automation for project wiki creation
- Fix: Serve favicon image always from the main GitLab domain to avoid issues with CORS
- Fix diff comment alignment for parallel code additions
- Fix Prometheus installation on Clusters
- Fix navigation bar links get underline style when active
- Fix custom logo rendering improperly on sign-in page
- Skips generation of MO files
- Fix multiple active tabs when Crowd or LDAP is in use
- Allow omnibus to disable sourcemaps in memory constrained environments
- Restore custom hooks for wiki
- Bump sprockets to
- Remove top padding on GPG popovers
- Fix notifications when MR becomes unmergeable
- Enforce setting string as value of the CI/CD variable
- Show a reCAPTCHA on signin page if custom header is set
- Notify conflict only for opened/locked merge requests
- Add support for verifying remote uploads, artifacts, and LFS objects in check rake tasks
- Use Go
1.10for source installations
- Fix alert button styling so that they don't show up white
- Enable webpack nodeEnv optimization
- Fix sorting by name on explore projects page.
- Fix a performance bottleneck in rendering wiki pages
Available in GitLab Starter, Premium, and Ultimate:
Available in GitLab Premium and Ultimate:
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.
Access to GitLab Starter, 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