Sep 27, 2017 - Jaroslava Kadlecová  

GitLab Patch Release: 10.0.2

Gitlab 10.0.2 patch release resolves a number of regressions and bugs in 10.0.1

Today we are releasing version 10.0.2 for GitLab Community Edition (CE) and Enterprise Edition (EE).

This version resolves a number of regressions and bugs in this month's 10.0.1 release and prior versions.

It includes the following fixes:

  • CE/EE: Resize comment form after note submit and discard it (!14401)
  • CE/EE: Fix rendering double note issue (!14429)
  • CE/EE: Ensure that Blob.raw returns always a valid blob object (!14412)
  • CE/EE: Remove navbar gradient (!14457)
  • CE/EE: Re-allow name attribute on user-provided anchor HTML (!14452)
  • CE/EE: Fix checks failing with 'undefined method run_command in rake gitlab:check (!14469)
  • CE/EE: Fix PG::UniqueViolation external_email migration (!14474)
  • CE/EE: Prevent URL concatenation for avatars (!14437)
  • CE/EE: IssueNotes: Switch back to Write pane when note cancel or submit (!14402)
  • CE/EE: Fix a dash being rendered in the note's access role (!14450)
  • CE/EE: Make locked setting of Runner to not affect jobs scheduling (!14483)
  • CE/EE: Avoid wrapping users in dropdown (!14410)
  • EE: Fix delta size check to handle commit or nil objects (!2976)
  • EE: Fix 500 error due to promote group Web hooks (!2972)
  • EE: Add notes on authentication to PG HA document (!2851)
  • EE: Send valid project path as name for Jira dev panel (!3005)
  • EE: Remove duplicate group boards doc (!2991)
  • EE: Point to embedded Consul (!2980)
  • EE: Fix internal link in docs(!3003)
  • Omnibus: Fix an issue where enabling a GitLab Geo role would also disable all default services (!1963)
  • Omnibus: Add option to configure redis snapshot frequency (!1964)
  • Omnibus: Update pg-upgrade output to be more clear when a bundled PostgreSQL is not in use (!1962)
  • Omnibus: Reload consul on config change instead of restarting (!1966)

Upgrade barometer

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 /etc/gitlab/skip-auto-migrations file.


To update, check out our update page.

Enterprise Edition

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

Take GitLab for a spin

See what your team could do with The DevSecOps Platform.

Get free trial

Have a question? We're here to help.

Talk to an expert
Edit this page View source