GitLab 8.3.3 Released

Warning (2016-01-12 13:25 UTC): Do not upgrade to GitLab 8.3.3 at this time. GitLab 8.3.3 ships with gitlab-workhorse 0.5.3, which contains an API routing bug. GitLab 8.3.4 has been released to correct the issue.

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

It includes the following changes:

• CE/EE: Preserve CE behavior with JIRA integration by only calling API if URL is set (#2341)
• CE/EE: Fix duplicated branch creation/deletion events when using Web UI (#2343)
• CE/EE: Add configurable LDAP server query timeout (#2267)
• CE/EE: Get "Merge when build succeeds" to work when commits were pushed to MR target branch while builds were running (#2304)
• CE/EE: Suppress e-mails on failed builds if allow_failure is set (#2178)
• CE/EE: Fix project transfer e-mail sending incorrect paths in e-mail notification (#2235)
• CE/EE: Enable "Add key" button when user fills in a proper key (#2208)
• CE/EE: Better support for referencing and closing issues in Asana service (#2111)
• CE/EE: Fix error in processing reply-by-email messages (#2288)
• CE/EE: Fix Error 500 when visiting build page of project with nil runners_token (#2294)
• CE/EE: Use WOFF versions of SourceSansPro fonts (#2357)
• CE/EE: Fix regression when builds were not generated for tags created through web/api interface (#2366)
• CE/EE: Bump gitlab-workhorse to 0.5.3 (#2367)
• EE: Fix undefined method call in Jenkins integration service (#106)

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.

Update gitlab-workhorse

This version requires gitlab-workhorse version 0.5.3. Omnibus installations will automatically have the latest version; installations from source should follow the update guide to ensure the required version is used.

Update Asana Tokens

Asana API Keys have been deprecated in favor of Personal Access Tokens and OAuth. You can create a personal access token for GitLab on the Apps tab of your profile settings.

Once you have a token, you can update all projects via the console:

AsanaService.all.each { |s| s.api_key = '[PERSONAL_ACCESS_TOKEN]'; s.save }

See #2111 for more details on this change.

Updating

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 included with a subscription. No time to upgrade GitLab yourself? Subscribers receive upgrade and installation services.