GitLab 8.3.3 Released

Jan 11, 2016

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:

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]'; }

See #2111 for more details on this change.


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.

Install GitLab on your own server in 2 minutes

Browse all posts

For the latest and most detailed news follow @gitlab on Twitter. Future blog posts suggestions.