GitLab 11.7 delivers Releases in GitLab Core. Users now have release snapshots that not only include the source code but all related artifacts.
This eliminates the need for manual collection of source code, build output, and other metadata or artifacts associated with a released version of your code. Additionally, Releases sets the stage for broader, more robust release orchestration in the future.
Multi-level Child Epics are the newest addition to GitLab portfolio management, available in Ultimate. Child Epics enable multi-level work breakdown structures, helping you manage more complex projects and workplans. You can now have an epic containing both issues and epics.
This structure enables a direct connection between planning and actionable issues to implement.
Gitlab 11.7 Premium delivers NPM registries directly in GitLab, providing a standard, more secure way to share and version control NPM packages across projects. Simply share the package name and NPM and GitLab handles the rest, all within a single interface!
And so much more
It is always so hard to pick which features are our top features in our monthly releases, so we are calling out a couple of additional cool features:
Remediate vulnerability with patch file: As you know, GitLab security features help you to detect vulnerabilities. With GitLab 11.7, you now have the ability to remediate that vulnerability and suggest a solution for Node.js projects managed with Yarn. While this is our first official remediation-type feature, you can be sure it is only just the beginning!
API integration with Kubernetes: If you are into creating a lot of Kubernetes clusters or consider yourself a Kubernetes ninja, we have a Kubernetes API to greatly reduce manual efforts and make your life a whole lot easier!
Cross-project pipeline browsing: With the ability to view pipelines across projects, the sky's the limit on what information is readily at your fingertips with this feature!
Read on for the complete list of features for GitLab 11.7!
Key features released in GitLab 11.7
Publish releases for your projects
Our new Releases feature adds the ability to create releases in GitLab and view them on a summary page. Releases are
a snapshot in time of the source, links, and other metadata or artifacts associated with a
released version of your code, and allow for users of your project to easily discover the latest released
version of your code.
Ruby 2.5 required
Beginning with GitLab 11.6, Ruby 2.5 is required to run
GitLab. Omnibus GitLab already ships with Ruby 2.5.3,
but users of source installations that run Ruby 2.4 will have to upgrade.
Dec. 22, 2018.
Debian 7 Wheezy support
GitLab 11.6 was the last release with support for Debian 7 Wheezy. Deprecation was originally announced in
Debian Wheezy is no longer supported by the Debian project
as of May 2018, we strongly recommend users to upgrade to
Stretch or Jessie.
Dec. 22, 2019
Raspbian Jessie support
GitLab 11.8 will be the last release with support for Raspbian Jessie.
Jessie has transitioned to LTS, and the
latest Raspbian Jessie image is over a year old.
We recommend that users upgrade to Raspbian Stretch.
Feb. 22, 2019
CentOS 6 support for GitLab Runner using the Docker executor
will be the last release with Runner support for CentOS 6 when using
the Docker executor because we are planning to update to a more current
Docker library which no longer supports it. Please see this
Mar. 22, 2019
Support for Prometheus 1.x in Omnibus GitLab
With GitLab 11.4, the bundled Prometheus 1.0 version is
deprecated in Omnibus GitLab. Prometheus 2.0 is now
included, however the metrics
format is incompatible with 1.0. Existing installations can upgrade to 2.0
and optionally migrate their data using an included
With GitLab 12.0, any installation not yet running Prometheus 2.0 will be
automatically upgraded. Metric data from Prometheus 1.0 will not be
migrated, and will be lost.
Jun. 22, 2019
TLS v1.1 will be disabled by default in 12.0
Beginning with GitLab 12.0, TLS v1.1 will be disabled by default
to improve security. This mitigates numerous issues including Heartbleed
and makes GitLab compliant out of the box with the PCI DSS 3.1 standard.
To disable TLS v1.1 immediately, set
nginx['ssl_protocols'] = "TLSv1.2" in
gitlab.rb and run
Jun. 22, 2019
OpenShift template for installing GitLab
gitlab helm chart is the recommended method for
operating GitLab on Kubernetes, including deployment on OpenShift.
The OpenShift template
for installing GitLab is deprecated, and will no longer be supported in GitLab 12.0.
Jun. 22, 2019
GitLab Geo will enforce Hashed Storage in GitLab 12.0
GitLab Geo requires Hashed
to mitigate race conditions on secondary nodes. This was noted in
In 11.5, we added this requirement to the Geo documentation:
sudo gitlab-rake gitlab:geo:check checks that Hashed
Storage is enabled and all projects are migrated:
you are using Geo, please run this check and migrate as soon as possible.
In 11.8, a permanently dismissable warning
will be displayed on the “Admin Area › Geo › Nodes” page if the above
checks are not resolved.
In 12.0, Geo will enforce the Hashed Storage requirement:
Jun. 22, 2019
Google OAuth2 SSO only supported in GitLab 11.7+
On Mar. 7, 2019, Google is shutting down all Google+ APIs. You can read
more about the announcement from Google here.
Since GitLab versions prior to 11.7 rely on these APIs for Google OAuth2,
Google single sign-on will no longer function on these versions. GitLab
11.7 and beyond will support Google SSO.
If your instance relies on Google OAuth2 for authentication, we recommend
upgrading to 11.7.
Mar. 7, 2019
Editing/deleting Git tags on non-protected branches has been historically
restricted to Maintainers and Owners.
Since Developers can add tags as well as modify and remove non-protected
branches, Developers should be able to modify and remove Git tags as well.
In GitLab 11.9, we’re making this change to our permissions model to improve
workflow and help developers make better and more effective use of tags.
Mar. 22, 2019
Hipchat will be discontinued. So we
are removing the existing GitLab Hipchat integration feature as part of the 11.9 release.
Mar. 22, 2019
To upgrade to GitLab 11.7 from the latest 11.6 version, no downtime is required. Consult the documentation on upgrades without downtime.
Database migrations in this release may take between 30 and 60 minutes for
instances similar to the size of GitLab.com. For smaller instances, the
total time should be no more than roughly 15 minutes.
GitLab Geo users, please consult the documentation on upgrading Geo.