Today we are releasing version 14.0.5 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 14.0 release and prior versions.
GitLab Community Edition and Enterprise Edition
- Resolve "404 for package details link under Infrastructure Registry for projects nested under 2 group levels"
- Resolve "Terraform module usage instructions are incorrect"
- Add documentation for boards epic create
- Initialize conversion of ci_builds_metadata.id for bigint migration
- Fix git clone for projects with a trailing dot over HTTP
- Do not create audit event for failed logins on read-only DB
- Add prefix to autocomplete path
- Return empty strings for Jira links when URL is not set
- Fix libmagic not being able to find magic files
Important notes on upgrading
This version does not include any new migrations, and for multi-node deployments, 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 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