Today we're releasing version 8.17.2 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version resolves a bug in our previous patch where an invalid asset may have been cached in the web browser, causing errors in the user interface.
Please read on for more details.
The 8.17.1+ce.0
and 8.17.1+ee.0
packages contained an invalid asset, causing
JavaScript errors when the site was accessed. This asset has been corrected in
the 8.17.1+ce.2
and 8.17.1+ee.2
packages, but if you installed the previous
packages, you would continue to encounter errors due to outdated assets being
cached by the browser.
This patch includes a fix that will cause users' browsers to use the new asset instead of the invalid one. It also includes one additional bug fix for GitLab CI.
Upgrade barometer
This version does not include any migrations and does not require 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.
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.
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