GitLab Major Releases

<br />
<b>Deprecated</b>:  Function get_magic_quotes_gpc() is deprecated in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>99</b><br />
<br />
<b>Deprecated</b>:  The each() function is deprecated. This message will be suppressed on further calls in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>619</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>832</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<br />
<b>Warning</b>:  Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in <b>/hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php</b> on line <b>839</b><br />
<?xml version='1.0' encoding='utf-8' ?>
<feed xmlns='http://www.w3.org/2005/Atom'>
<title>GitLab Major Releases</title>
<id>https://about.gitlab.com/releases</id>
<link href='https://about.gitlab.com/releases/categories/releases/' />
<updated>2025-10-16T00:00:00+00:00</updated>
<author>
<name>The GitLab Team</name>
</author>
<entry>
<title>GitLab 18.5 released with GitLab Duo Planner Agent (beta) and GitLab Duo Security Analyst Agent (beta)</title>
<release>18.5</release>
<link href='https://about.gitlab.com/releases/2025/10/16/gitlab-18-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/10/16/gitlab-18-5-released/</id>
<published>2025-10-16T00:00:00+00:00</published>
<author>
<name>Rutvik Shah</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 18.5 with the &lt;a href=&quot;#gitlab-duo-planner-a-specialized-agent-and-product-manager-team-member-beta&quot;&gt;GitLab Duo Planner Agent (beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-security-analyst-agent-for-duo-agent-catalog-beta&quot;&gt;GitLab Duo Security Analyst Agent (beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#maven-virtual-registry-now-available-in-beta&quot;&gt;Maven virtual registry UI (beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#pick-up-where-you-left-off-on-the-new-personal-homepage&quot;&gt;personal homepage&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 57 improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 278 contributions you provided to GitLab 18.5!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Tune in to the GitLab Developer Show on October 28 at 10:00am PT, where we’ll dive into the latest features in GitLab 18.5 and share how we’re cultivating a thriving community of contributors. See features in action, ask your questions and get insights from our team in real time, and discover how you can grow with GitLab.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;www.linkedin.com&#x2F;events&#x2F;interviewwithkelseyhightowerand7384290169035788288&#x2F;theater&#x2F;&quot;&gt;RSVP Here&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_5&#x2F;18_5-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 18.4 released with GitLab Duo Model Selection and GitLab Knowledge Graph</title>
<release>18.4</release>
<link href='https://about.gitlab.com/releases/2025/09/18/gitlab-18-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/09/18/gitlab-18-4-released/</id>
<published>2025-09-18T00:00:00+00:00</published>
<author>
<name>Sampath Ranasinghe</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;
&lt;p&gt;&lt;strong&gt;New as of September 23&lt;&#x2F;strong&gt;: We&#x27;ve introduced the GitLab Duo AI Catalog, a central library where teams can create, share, and collaborate with custom-built agents across their organization.&lt;&#x2F;p&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 18.4 with &lt;a href=&quot;#gitlab-duo-model-selection-now-generally-available&quot;&gt;GitLab Duo Model Selection now generally available&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-knowledge-graph&quot;&gt;GitLab Knowledge Graph&lt;&#x2F;a&gt;, &lt;a href=&quot;#end-user-model-selection-now-available-with-gitlab-duo&quot;&gt;End user model selection now available with GitLab Duo&lt;&#x2F;a&gt;, &lt;a href=&quot;#cicd-job-tokens-can-authenticate-git-push-requests&quot;&gt;CI&#x2F;CD job tokens can authenticate Git push requests&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitLab-duo-ai-catalog&quot;&gt;Duo AI Catalog&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 24 improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 136 contributions you provided to GitLab 18.4!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;Q&amp;amp;A + Code: Exploring GitLab 18.4 and Growing the Contributor’s Garden&lt;&#x2F;strong&gt;&lt;&#x2F;p&gt;

&lt;p&gt;Tune in to the &lt;strong&gt;GitLab Developer Show&lt;&#x2F;strong&gt;, where we’ll dive into the latest features in GitLab 18.4 and share how we’re cultivating a thriving community of contributors. See features in action, get insights from our team, and discover how you can grow with GitLab.&lt;&#x2F;p&gt;

&lt;p&gt;👉 &lt;a href=&quot;https:&#x2F;&#x2F;www.linkedin.com&#x2F;events&#x2F;7373772262312906753&#x2F;&quot;&gt;Watch Now&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_4&#x2F;18_4-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 18.3 released with Duo Agent Platform in Visual Studio (Beta) and Embedded views</title>
<release>18.3</release>
<link href='https://about.gitlab.com/releases/2025/08/21/gitlab-18-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/08/21/gitlab-18-3-released/</id>
<published>2025-08-21T00:00:00+00:00</published>
<author>
<name>Grant Hickman</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 18.3 with &lt;a href=&quot;#duo-agent-platform-in-visual-studio-beta&quot;&gt;Duo Agent Platform in Visual Studio (Beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#embedded-views-powered-by-glql&quot;&gt;Embedded views&lt;&#x2F;a&gt;, &lt;a href=&quot;#migration-by-direct-transfer&quot;&gt;Migration by direct transfer&lt;&#x2F;a&gt;, &lt;a href=&quot;#fine-grained-permissions-for-cicd-job-tokens&quot;&gt;Fine-grained permissions for CI&#x2F;CD job tokens&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 38 improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 314 contributions you provided to GitLab 18.3!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_3&#x2F;18_3-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 18.2 released with Duo Agent Platform in the IDE (Beta) and Custom workflow statuses for issues and tasks</title>
<release>18.2</release>
<link href='https://about.gitlab.com/releases/2025/07/17/gitlab-18-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/07/17/gitlab-18-2-released/</id>
<published>2025-07-17T00:00:00+00:00</published>
<author>
<name>Gabriel Engel</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 18.2 with &lt;a href=&quot;#duo-agent-platform-in-the-ide-beta&quot;&gt;Duo Agent Platform in the IDE (Beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#custom-workflow-statuses-for-issues-and-tasks&quot;&gt;Custom workflow statuses for issues and tasks&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-merge-request-homepage&quot;&gt;New merge request homepage&lt;&#x2F;a&gt;, &lt;a href=&quot;#improve-security-with-immutable-container-tags&quot;&gt;Immutable container tags for improved security&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 152 contributions you provided to GitLab 18.2!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_2&#x2F;product-gl18-release-cover-18-2-0750-1440x400-fy26.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 18.1 released with Maven virtual registry (beta) and Duo Code Review</title>
<release>18.1</release>
<link href='https://about.gitlab.com/releases/2025/06/19/gitlab-18-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/06/19/gitlab-18-1-released/</id>
<published>2025-06-19T00:00:00+00:00</published>
<author>
<name>Tim Rizzi</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 18.1 with &lt;a href=&quot;#maven-virtual-registry-now-available-in-beta&quot;&gt;Maven virtual registry (beta)&lt;&#x2F;a&gt;, &lt;a href=&quot;#duo-code-review-is-now-generally-available&quot;&gt;Duo Code Review&lt;&#x2F;a&gt;, &lt;a href=&quot;#compromised-password-detection-for-native-gitlab-credentials&quot;&gt;compromised password detection&lt;&#x2F;a&gt;, and &lt;a href=&quot;#achieve-slsa-level-1-compliance-with-cicd-components&quot;&gt;SLSA level 1 with components&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 110+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 311 contributions you provided to GitLab 18.1!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_1&#x2F;product-gl18-release-cover-18-1-0750-1440x400-fy26.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 18.0 released with GitLab Duo for Premium and Ultimate</title>
<release>18.0</release>
<link href='https://about.gitlab.com/releases/2025/05/15/gitlab-18-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/05/15/gitlab-18-0-released/</id>
<published>2025-05-15T00:00:00+00:00</published>
<author>
<name>Jeff Tucker</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 18.0 with &lt;a href=&quot;#gitlab-premium-and-ultimate-with-duo&quot;&gt;GitLab Premium and Ultimate with Duo&lt;&#x2F;a&gt;, &lt;a href=&quot;#automatic-reviews-with-duo-code-review&quot;&gt;Automatic reviews with Duo Code Review&lt;&#x2F;a&gt;, &lt;a href=&quot;#improved-duo-code-review-context&quot;&gt;Improved Duo Code Review context&lt;&#x2F;a&gt;, &lt;a href=&quot;#repository-x-ray-now-available-on-gitlab-duo-self-hosted&quot;&gt;Repository X-Ray now available on Gitlab Duo Self-Hosted&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 328 contributions you provided to GitLab 18.0!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;Come see what we’ve added in GitLab 18 to help you get the benefits of AI across the entire software delivery lifecycle and strengthen security without slowing developers down — all in one natively integrated DevSecOps platform. Register for the &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;eighteen&#x2F;?utm_medium=blog&amp;amp;utm_source=blog&amp;amp;utm_campaign=20250624_global_corp_webcast_aisdlc_en_gitlab18&amp;amp;utm_content=releasepost_x_x&quot;&gt;GitLab 18 virtual release event: The next step in intelligent DevSecOps&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;18_0&#x2F;product-gl18-release-cover-18-0-0750-1440x400-fy26.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.11 released with Custom Compliance Frameworks</title>
<release>17.11</release>
<link href='https://about.gitlab.com/releases/2025/04/17/gitlab-17-11-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/04/17/gitlab-17-11-released/</id>
<published>2025-04-17T00:00:00+00:00</published>
<author>
<name>Sara Meadzinger</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;about.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.11 with &lt;a href=&quot;#customize-compliance-frameworks-with-requirements-and-compliance-controls&quot;&gt;custom compliance frameworks&lt;&#x2F;a&gt;, &lt;a href=&quot;#more-gitlab-duo-features-now-available-on-gitlab-duo-self-hosted&quot;&gt;more AI features on GitLab Duo Self-Hosted&lt;&#x2F;a&gt;, &lt;a href=&quot;#epic-issue-and-task-custom-fields&quot;&gt;custom epic, issue, and task fields&lt;&#x2F;a&gt;, &lt;a href=&quot;#cicd-pipeline-inputs&quot;&gt;CI&#x2F;CD pipeline inputs&lt;&#x2F;a&gt;, &lt;a href=&quot;#service-accounts-ui&quot;&gt;service accounts UI&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 60+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 284 contributions you provided to GitLab 17.11!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_11&#x2F;product-gl17-blog-release-cover-17-11-0093-1800x945-fy25.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.10 released with Duo Code Review &amp; Root Cause Analysis</title>
<release>17.10</release>
<link href='https://about.gitlab.com/releases/2025/03/20/gitlab-17-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/03/20/gitlab-17-10-released/</id>
<published>2025-03-20T00:00:00+00:00</published>
<author>
<name>Tim Rizzi</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.10 with &lt;a href=&quot;#duo-code-review-available-in-beta&quot;&gt;Duo Code Review Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#root-cause-analysis-available-on-gitlab-duo-self-hosted&quot;&gt;Root Cause Analysis for GitLab Duo Self-Hosted&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-query-language-views-beta&quot;&gt;GitLab Query Language (GLQL) Views Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-visualization-of-devops-performance-with-dora-metrics-across-projects&quot;&gt;New Visualization of DevOps Performance with DORA Metrics&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 120+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 205+ contributions you provided to GitLab 17.10!&lt;&#x2F;p&gt;

&lt;p&gt;At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_10&#x2F;17_10-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.9 released with GitLab Duo Self-Hosted available in GA</title>
<release>17.9</release>
<link href='https://about.gitlab.com/releases/2025/02/20/gitlab-17-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/02/20/gitlab-17-9-released/</id>
<published>2025-02-20T00:00:00+00:00</published>
<author>
<name>Rutvik Shah</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.9 with &lt;a href=&quot;#gitlab-duo-self-hosted-is-generally-available&quot;&gt;GitLab Duo Self-Hosted available in GA&lt;&#x2F;a&gt;, &lt;a href=&quot;#run-multiple-pages-sites-with-parallel-deployments&quot;&gt;the ability to run multiple GitLab Pages sites with parallel deployments&lt;&#x2F;a&gt;, &lt;a href=&quot;#add-project-files-to-duo-chat-in-vs-code-and-jetbrains-ides&quot;&gt;the option to add project files to Duo Chat in VS Code and JetBrains IDEs&lt;&#x2F;a&gt;, &lt;a href=&quot;#automatic-cicd-pipeline-cleanup&quot;&gt;automatic deletion of older pipelines&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 110+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 322 contributions you provided to GitLab 17.9!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_9&#x2F;product-gl17-blog-release-cover-17-9-0093-1800x945-fy25.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.8 released with improved container repository security</title>
<release>17.8</release>
<link href='https://about.gitlab.com/releases/2025/01/16/gitlab-17-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2025/01/16/gitlab-17-8-released/</id>
<published>2025-01-16T00:00:00+00:00</published>
<author>
<name>Joe Randazzo</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.8 including &lt;a href=&quot;#enhance-security-with-protected-container-repositories&quot;&gt;enhanced security for container repositories&lt;&#x2F;a&gt;, &lt;a href=&quot;#list-the-deployments-related-to-a-release&quot;&gt;list deployments related to a release&lt;&#x2F;a&gt;, &lt;a href=&quot;#machine-learning-model-experiments-tracking-in-ga&quot;&gt;ML model experiments tracking&lt;&#x2F;a&gt;, &lt;a href=&quot;#hosted-runners-on-linux-for-gitlab-dedicated-now-in-limited-availability&quot;&gt;Hosted runners on Linux for GitLab Dedicated&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 60+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 121 contributions you provided to GitLab 17.8!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.9 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_8&#x2F;product-gl17-release-cover-17-8-0093-1440x400-fy25.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.7 released with new Planner user role</title>
<release>17.7</release>
<link href='https://about.gitlab.com/releases/2024/12/19/gitlab-17-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/12/19/gitlab-17-7-released/</id>
<published>2024-12-19T00:00:00+00:00</published>
<author>
<name>Courtney Meddaugh</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.7 with a &lt;a href=&quot;#new-planner-user-role&quot;&gt;new Planner user role&lt;&#x2F;a&gt;, &lt;a href=&quot;#auto-resolve-vulnerabilities-when-not-found-in-subsequent-scans&quot;&gt;auto-resolution policy for vulnerabilities&lt;&#x2F;a&gt;, &lt;a href=&quot;#instance-administrators-can-control-which-integrations-can-be-enabled&quot;&gt;admin-controlled instance integration allowlists&lt;&#x2F;a&gt;, &lt;a href=&quot;#rotate-personal-project-and-group-access-tokens-in-the-ui&quot;&gt;access token rotation in the UI&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 230+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 138 contributions you provided to GitLab 17.7!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.8 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_7&#x2F;17_7-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.6 released with self-hosted Duo Chat in beta</title>
<release>17.6</release>
<link href='https://about.gitlab.com/releases/2024/11/21/gitlab-17-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/11/21/gitlab-17-6-released/</id>
<published>2024-11-21T00:00:00+00:00</published>
<author>
<name>Magdalena Frankiewicz</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.6 with &lt;a href=&quot;#use-self-hosted-model-for-gitlab-duo-chat&quot;&gt;self-hosted Duo Chat in beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-adherence-checks-for-sast-and-dast-security-scanners&quot;&gt;adherence checks for SAST and DAST security scanners&lt;&#x2F;a&gt;, &lt;a href=&quot;#vulnerability-report-grouping&quot;&gt;vulnerability report grouping&lt;&#x2F;a&gt;, &lt;a href=&quot;#model-registry-now-generally-available&quot;&gt;generally available model registry&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from nearly 150 improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 265 contributions you provided to GitLab 17.6!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.7 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_6&#x2F;17_6-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.5 released with Duo Quick Chat AI code assistance.</title>
<release>17.5</release>
<link href='https://about.gitlab.com/releases/2024/10/17/gitlab-17-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/10/17/gitlab-17-5-released/</id>
<published>2024-10-17T00:00:00+00:00</published>
<author>
<name>John Crowley</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 17.5 with &lt;a href=&quot;#introducing-duo-quick-chat&quot;&gt;code assistance in IDEs from GitLab Duo Quick Chat&lt;&#x2F;a&gt;, &lt;a href=&quot;#use-self-hosted-model-for-gitlab-duo-code-suggestions&quot;&gt;self-hosted models for GitLab Duo Code Suggestions&lt;&#x2F;a&gt;, &lt;a href=&quot;#export-code-suggestion-usage-events&quot;&gt;export code suggestion usage events&lt;&#x2F;a&gt;, &lt;a href=&quot;#have-a-conversation-with-gitlab-duo-chat-about-your-merge-request&quot;&gt;MR conversations with GitLab Duo Chat&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 125+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 200 contributions you provided to GitLab 17.5!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.6 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_5&#x2F;17_5-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.4 released with improved context in GitLab Duo</title>
<release>17.4</release>
<link href='https://about.gitlab.com/releases/2024/09/19/gitlab-17-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/09/19/gitlab-17-4-released/</id>
<published>2024-09-19T00:00:00+00:00</published>
<author>
<name>Alex Martin</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 17.4 with &lt;a href=&quot;#more-context-aware-gitlab-duo-code-suggestions-using-open-tabs&quot;&gt;more context-aware Code Suggestions using open tabs&lt;&#x2F;a&gt;, &lt;a href=&quot;#auto-merge-when-all-checks-pass&quot;&gt;auto-merging when all checks pass&lt;&#x2F;a&gt;, &lt;a href=&quot;#extension-marketplace-now-available-in-the-web-ide&quot;&gt;extension marketplace in the Web IDE&lt;&#x2F;a&gt;, &lt;a href=&quot;#advanced-sast-is-generally-available&quot;&gt;Advanced SAST generally available&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 140+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 220+ contributions you provided to GitLab 17.4!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month&#x27;s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.5 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_4&#x2F;17_4-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.3 released with GitLab Duo Root Cause Analysis</title>
<release>17.3</release>
<link href='https://about.gitlab.com/releases/2024/08/15/gitlab-17-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/08/15/gitlab-17-3-released/</id>
<published>2024-08-15T00:00:00+00:00</published>
<author>
<name>Gabe Weaver</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.3 with &lt;a href=&quot;#troubleshoot-failed-jobs-with-root-cause-analysis&quot;&gt;GitLab Duo-powered root cause analysis for failed pipeline jobs&lt;&#x2F;a&gt;, &lt;a href=&quot;#resolve-a-vulnerability-with-ai&quot;&gt;AI-assisted vulnerability resolution&lt;&#x2F;a&gt;, &lt;a href=&quot;#ai-impact-analytics-code-suggestions-acceptance-rate-and-gitlab-duo-seats-usage&quot;&gt;AI impact analytics for Code Suggestions acceptance rate and GitLab Duo seats usage&lt;&#x2F;a&gt;, &lt;a href=&quot;#add-multiple-compliance-frameworks-to-a-single-project&quot;&gt;the ability to add multiple compliance frameworks to a single project&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 160+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 130+ contributions you provided to GitLab 17.3!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.4 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_3&#x2F;17-3-cover.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.2 released with log streaming, a new pipeline execution security policy, and vulnerability explanations now generally available</title>
<release>17.2</release>
<link href='https://about.gitlab.com/releases/2024/07/18/gitlab-17-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/07/18/gitlab-17-2-released/</id>
<published>2024-07-18T00:00:00+00:00</published>
<author>
<name>Viktor Nagy</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.2 with &lt;a href=&quot;#vulnerability-explanation&quot;&gt;vulnerability explanations becoming generally available and integrated with GitLab Duo&lt;&#x2F;a&gt; to help understand SAST vulnerabilities, &lt;a href=&quot;#log-streaming-for-kubernetes-pods-and-containers&quot;&gt;log streaming support for Kubernetes&lt;&#x2F;a&gt; to help troubleshoot workloads without leaving GitLab, a new &lt;a href=&quot;#pipeline-execution-policy-type&quot;&gt;pipeline execution security policy type&lt;&#x2F;a&gt; to enforce the execution of CI&#x2F;CD jobs in pipelines, &lt;a href=&quot;#gitlab-duo-chat-and-code-suggestions-available-in-workspaces&quot;&gt;Duo Chat and Code Suggestions support in GitLab workspaces&lt;&#x2F;a&gt; for a productivity boost in the remote development environment, and much more!
These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 160+ contributions you provided to GitLab 17.2!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt;, and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month&#x27;s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.3 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_2&#x2F;17-2-cover.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.1 released with Model registry available in beta and multiple GitLab Duo Code Suggestions in VS Code</title>
<release>17.1</release>
<link href='https://about.gitlab.com/releases/2024/06/20/gitlab-17-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/06/20/gitlab-17-1-released/</id>
<published>2024-06-20T00:00:00+00:00</published>
<author>
<name>Gabriel Engel</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.1 with &lt;a href=&quot;#model-registry-available-in-beta&quot;&gt;Model registry available in beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#see-multiple-gitlab-duo-code-suggestions-in-vs-code&quot;&gt;multiple GitLab Duo Code Suggestions in VS Code&lt;&#x2F;a&gt;, &lt;a href=&quot;#secret-push-protection-available-in-beta&quot;&gt;Secret Push Protection available in beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-runner-autoscaler-is-generally-available&quot;&gt;GitLab Runner Autoscaler is generally available&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 45+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 340+ contributions you provided to GitLab 17.1!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.2 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_1&#x2F;17_1-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 17.0 released with generally available CI&#x2F;CD Catalog and AI Impact analytics dashboard</title>
<release>17.0</release>
<link href='https://about.gitlab.com/releases/2024/05/16/gitlab-17-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/05/16/gitlab-17-0-released/</id>
<published>2024-05-16T00:00:00+00:00</published>
<author>
<name>Gabriel Engel</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 17.0 with &lt;a href=&quot;#cicd-catalog-with-components-and-inputs-now-generally-available&quot;&gt;generally available CI&#x2F;CD Catalog&lt;&#x2F;a&gt;, &lt;a href=&quot;#ai-impact-analytics-in-the-value-streams-dashboard&quot;&gt;AI Impact analytics dashboard&lt;&#x2F;a&gt;, &lt;a href=&quot;#introducing-hosted-runners-on-linux-arm&quot;&gt;hosted runners on Linux Arm&lt;&#x2F;a&gt;, &lt;a href=&quot;#introducing-deployment-detail-pages&quot;&gt;deployment detail pages&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 60+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the unbelievable 344 contributions you provided to GitLab 17.0!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;Join us to explore the new AI-powered features in GitLab 17 that will help you improve collaboration, visibility, security, and cycle times. Register for the &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;seventeen&#x2F;&quot;&gt;GitLab 17 release virtual event: The future of AI-driven software development&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.1 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;17_0&#x2F;17_0-cover-image.svg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.11 released with GitLab Duo Chat general availability</title>
<release>16.11</release>
<link href='https://about.gitlab.com/releases/2024/04/18/gitlab-16-11-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/04/18/gitlab-16-11-released/</id>
<published>2024-04-18T00:00:00+00:00</published>
<author>
<name>Loryn Bortins</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.11 with &lt;a href=&quot;#gitlab-duo-chat-now-generally-available&quot;&gt;GitLab Duo Chat general availability&lt;&#x2F;a&gt;, &lt;a href=&quot;#understand-your-users-better-with-product-analytics&quot;&gt;Product Analytics general availability&lt;&#x2F;a&gt;, &lt;a href=&quot;#security-policy-scopes&quot;&gt;Security policy scopes&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 190+ contributions you provided to GitLab 16.11!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 17.0 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_11&#x2F;16_11-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.10 released with semantic versioning in the CI&#x2F;CD catalog</title>
<release>16.10</release>
<link href='https://about.gitlab.com/releases/2024/03/21/gitlab-16-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/03/21/gitlab-16-10-released/</id>
<published>2024-03-21T00:00:00+00:00</published>
<author>
<name>Torsten Linz</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.10 with &lt;a href=&quot;#semantic-versioning-in-the-cicd-catalog&quot;&gt;semantic versioning coming to the CI&#x2F;CD catalog&lt;&#x2F;a&gt;, &lt;a href=&quot;#wiki-templates&quot;&gt;wiki templates&lt;&#x2F;a&gt;, &lt;a href=&quot;#offload-ci-traffic-to-geo-secondaries&quot;&gt;the possibility to offload CI traffic to geo secondaries&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-clickhouse-integration-for-high-performance-devops-analytics&quot;&gt;new ClickHouse integration for high-performance DevOps analytics&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 90+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 170+ contributions you provided to GitLab 16.10!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.11 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_10&#x2F;16_10-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.9 released with wider Beta access for Duo Chat</title>
<release>16.9</release>
<link href='https://about.gitlab.com/releases/2024/02/15/gitlab-16-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/02/15/gitlab-16-9-released/</id>
<published>2024-02-15T00:00:00+00:00</published>
<author>
<name>Tim Rizzi</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.9 with &lt;a href=&quot;#gitlab-duo-chat-beta-now-available-in-premium&quot;&gt;GitLab Duo Chat&lt;&#x2F;a&gt; now available for Premium SaaS and self-managed customers, the ability to &lt;a href=&quot;#request-changes-on-merge-requests&quot;&gt;request changes in a merge request&lt;&#x2F;a&gt; without blocking the merge, &lt;a href=&quot;#improvements-to-the-cicd-variables-user-interface&quot;&gt;usability improvements to the CI&#x2F;CD variables page&lt;&#x2F;a&gt;, &lt;a href=&quot;#expanded-options-for-auto-canceling-pipelines&quot;&gt;more options for auto-canceling pipelines&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 80+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 200+ contributions you provided to GitLab 16.9!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.10 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_9&#x2F;16_9-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.8 released with Google Cloud Secret Manager support and the ability to speed up your builds with the Maven dependency proxy</title>
<release>16.8</release>
<link href='https://about.gitlab.com/releases/2024/01/18/gitlab-16-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2024/01/18/gitlab-16-8-released/</id>
<published>2024-01-18T00:00:00+00:00</published>
<author>
<name>Jocelyn Eillis</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.8 with &lt;a href=&quot;#google-cloud-secret-manager-support&quot;&gt;Google Cloud Secret Manager support&lt;&#x2F;a&gt;, &lt;a href=&quot;#speed-up-your-builds-with-the-maven-dependency-proxy&quot;&gt;the ability to speed up your builds with the Maven dependency proxy&lt;&#x2F;a&gt;, &lt;a href=&quot;#workspaces-are-now-generally-available&quot;&gt;general availability of Workspaces&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-organization-level-devops-view-with-dora-based-industry-benchmarks&quot;&gt;
new organization-level DevOps view with DORA-based industry benchmarks&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 207 contributions you provided to GitLab 16.8!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.9 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_8&#x2F;16_8-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.7 released with general availability of GitLab Duo Code Suggestions and CI&#x2F;CD Catalog in Beta</title>
<release>16.7</release>
<link href='https://about.gitlab.com/releases/2023/12/21/gitlab-16-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/12/21/gitlab-16-7-released/</id>
<published>2023-12-21T00:00:00+00:00</published>
<author>
<name>Jocelyn Eillis</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.7 with &lt;a href=&quot;#gitlab-duo-code-suggestions-is-generally-available&quot;&gt;general availability of GitLab Duo Code Suggestions&lt;&#x2F;a&gt;, &lt;a href=&quot;#cicd-catalog-beta-release&quot;&gt;CI&#x2F;CD Catalog in Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-drill-down-view-from-insights-report-charts&quot;&gt;new drill-down view from Insights report charts&lt;&#x2F;a&gt;, &lt;a href=&quot;#sast-results-in-mr-changes-view&quot;&gt;SAST findings in MR changes view&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 186 contributions you provided to GitLab 16.7!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.8 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_7&#x2F;16_7-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.6 released with GitLab Duo Chat available in Beta</title>
<release>16.6</release>
<link href='https://about.gitlab.com/releases/2023/11/16/gitlab-16-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/11/16/gitlab-16-6-released/</id>
<published>2023-11-16T00:00:00+00:00</published>
<author>
<name>Matthew Macfarlane</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.6 with &lt;a href=&quot;#gitlab-duo-chat-available-in-beta&quot;&gt;GitLab Duo Chat Available in Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#allow-users-to-enforce-mr-approvals-as-a-compliance-policy&quot;&gt;MR approvals as a compliance policy&lt;&#x2F;a&gt;, &lt;a href=&quot;#minimal-forking-only-include-the-default-branch&quot;&gt;improved forking&lt;&#x2F;a&gt;, &lt;a href=&quot;#improved-ui-for-cicd-variable-management&quot;&gt;improved UI for CI&#x2F;CD variable management&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 137 contributions you provided to GitLab 16.6!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.7 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_6&#x2F;16_6-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.5 released with compliance standards adherence reports and merge request target branch rules</title>
<release>16.5</release>
<link href='https://about.gitlab.com/releases/2023/10/22/gitlab-16-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/10/22/gitlab-16-5-released/</id>
<published>2023-10-22T00:00:00+00:00</published>
<author>
<name>Kai Armstrong</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.5 with &lt;a href=&quot;#compliance-standards-adherence-report&quot;&gt;compliance standards adherence reports&lt;&#x2F;a&gt;, &lt;a href=&quot;#create-rules-to-set-target-branches-for-merge-requests&quot;&gt;merge request target branch rules&lt;&#x2F;a&gt;, &lt;a href=&quot;#resolve-an-issue-thread&quot;&gt;resolvable issue threads&lt;&#x2F;a&gt;, &lt;a href=&quot;#fast-forward-merge-trains-with-semi-linear-history&quot;&gt;fast-forward merge trains with semi-linear history&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 170+ contributions you provided to GitLab 16.5!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.6 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_5&#x2F;16_5-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.4 released with customizable roles and group-level dependency list</title>
<release>16.4</release>
<link href='https://about.gitlab.com/releases/2023/09/22/gitlab-16-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/09/22/gitlab-16-4-released/</id>
<published>2023-09-22T00:00:00+00:00</published>
<author>
<name>Grant Hickman</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 16.4 with &lt;a href=&quot;#customizable-roles&quot;&gt;Customizable Roles&lt;&#x2F;a&gt;, &lt;a href=&quot;#groupsub-group-level-dependency-list&quot;&gt;Group&#x2F;sub-group level dependency list&lt;&#x2F;a&gt;, &lt;a href=&quot;#access-clusters-locally-using-your-gitlab-user-identity&quot;&gt;Access clusters locally using your GitLab user identity&lt;&#x2F;a&gt;, &lt;a href=&quot;#create-workspaces-for-private-projects&quot;&gt;Create workspaces for private projects&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 100+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To the wider GitLab community, thank you for the 137 contributions you provided to GitLab 16.4!
At GitLab, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;everyone can contribute&lt;&#x2F;a&gt; and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.5 release kickoff video.&lt;&#x2F;p&gt;

&lt;p&gt;Note that our monthly release date will change to the &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;gitlab-release-date-change&#x2F;&quot;&gt;third Thursday of every month&lt;&#x2F;a&gt; starting with our 16.6 release.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_4&#x2F;16_4-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.3 released with new velocity metrics in the Value Streams Dashboard</title>
<release>16.3</release>
<link href='https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/</id>
<published>2023-08-22T00:00:00+00:00</published>
<author>
<name>Sampath Ranasinghe</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.3 with &lt;a href=&quot;#new-velocity-metrics-in-the-value-streams-dashboard&quot;&gt;new velocity metrics in the Value Streams Dashboard&lt;&#x2F;a&gt;, &lt;a href=&quot;#more-powerful-gitlab-saas-runners-on-linux&quot;&gt;more powerful GitLab SaaS runners on Linux&lt;&#x2F;a&gt;, &lt;a href=&quot;#additional-filtering-for-scan-result-policies&quot;&gt;additional filtering for scan result policies&lt;&#x2F;a&gt;, &lt;a href=&quot;#connect-to-a-workspace-with-ssh&quot;&gt;workspace connections with SSH&lt;&#x2F;a&gt;, &lt;a href=&quot;#flux-sync-status-visualization&quot;&gt;Flux sync status visualization&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 100+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 237 contributions they provided to GitLab 16.3! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.4 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_3&#x2F;16_3-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.2 released with all new rich text editor experience</title>
<release>16.2</release>
<link href='https://about.gitlab.com/releases/2023/07/22/gitlab-16-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/07/22/gitlab-16-2-released/</id>
<published>2023-07-22T00:00:00+00:00</published>
<author>
<name>Tatyana Golubeva</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.2 with &lt;a href=&quot;#all-new-rich-text-editor-experience&quot;&gt;all new rich text editor experience&lt;&#x2F;a&gt;, &lt;a href=&quot;#command-palette&quot;&gt;command palette&lt;&#x2F;a&gt;, &lt;a href=&quot;#support-for-keyless-signing-with-cosign&quot;&gt;support for keyless signing with Cosign&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-customization-layer-for-the-value-streams-dashboard&quot;&gt;new customization layer for the Value Streams Dashboard&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 110+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 208 contributions they provided to GitLab 16.2! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.3 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_2&#x2F;16_2-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.1 released with all new navigation</title>
<release>16.1</release>
<link href='https://about.gitlab.com/releases/2023/06/22/gitlab-16-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/06/22/gitlab-16-1-released/</id>
<published>2023-06-22T00:00:00+00:00</published>
<author>
<name>Chris Balane</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 16.1 with &lt;a href=&quot;#all-new-navigation-experience&quot;&gt;all new navigation&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-dedicated-is-now-generally-available&quot;&gt;GitLab Dedicated General Availability&lt;&#x2F;a&gt;, &lt;a href=&quot;#visualize-kubernetes-resources-in-gitlab&quot;&gt;Kubernetes resource visualization&lt;&#x2F;a&gt;, &lt;a href=&quot;#authenticate-with-service-accounts&quot;&gt;Authentication with Service Accounts&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 100+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 189 contributions they provided to GitLab 16.1! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.2 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_1&#x2F;16_1-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 16.0 released with Value Streams Dashboards and improvements to AI-powered Code Suggestions</title>
<release>16.0</release>
<link href='https://about.gitlab.com/releases/2023/05/22/gitlab-16-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/05/22/gitlab-16-0-released/</id>
<published>2023-05-22T00:00:00+00:00</published>
<author>
<name>Kai Armstrong</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 16.0 with &lt;a href=&quot;#value-streams-dashboard-is-now-generally-available&quot;&gt;Value Streams Dashboards now generally available&lt;&#x2F;a&gt;, &lt;a href=&quot;#remote-development-workspaces-available-in-beta-for-public-projects&quot;&gt;Remote development workspaces&lt;&#x2F;a&gt;,
&lt;a href=&quot;#upsizing-gitlab-saas-runners-on-linux&quot;&gt;more powerful GitLab SaaS runners&lt;&#x2F;a&gt;, &lt;a href=&quot;#comment-templates&quot;&gt;comment templates&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;We&#x27;ve also made improvements to our &lt;a href=&quot;#code-suggestions-improvements&quot;&gt;AI-powered Code Suggestions&lt;&#x2F;a&gt;. This is just one of many &lt;a href=&quot;&#x2F;solutions&#x2F;ai&#x2F;&quot;&gt;AI-assisted features&lt;&#x2F;a&gt; we are iterating on to help you build more secure software, faster. Check out our ongoing &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;ai-ml-in-devsecops-series&#x2F;&quot;&gt;AI&#x2F;ML in DevSecOps Blog Series&lt;&#x2F;a&gt; to stay up-to-date between GitLab release announcements.&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 55+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 304 contributions they provided to GitLab 16.0! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.1 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;16_0&#x2F;16_0-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.11 released with Code Suggestions</title>
<release>15.11</release>
<link href='https://about.gitlab.com/releases/2023/04/22/gitlab-15-11-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/04/22/gitlab-15-11-released/</id>
<published>2023-04-22T00:00:00+00:00</published>
<author>
<name>Melissa Ushakov</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.11 with &lt;a href=&quot;#code-suggestions-for-ultimate--premium-users&quot;&gt;Code Suggestions&lt;&#x2F;a&gt;, &lt;a href=&quot;#manage-project-compliance-frameworks-report-at-group-level&quot;&gt;project compliance frameworks report management at the group level&lt;&#x2F;a&gt;, &lt;a href=&quot;#rerun-downstream-pipeline-trigger-jobs&quot;&gt;re-running downstream pipeline trigger jobs&lt;&#x2F;a&gt;, &lt;a href=&quot;#vulnerability-dismissal-reasons&quot;&gt;vulnerability dismissal reasons&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 110+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 180 contributions they provided to GitLab 15.11! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 16.0 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_11&#x2F;15_11-cover-image-sm.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.10 released with improved SAST finding resolution</title>
<release>15.10</release>
<link href='https://about.gitlab.com/releases/2023/03/22/gitlab-15-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/03/22/gitlab-15-10-released/</id>
<published>2023-03-22T00:00:00+00:00</published>
<author>
<name>Christina Lohr</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.10 with the ability to &lt;a href=&quot;#automatically-resolve-sast-findings-when-rules-are-disabled&quot;&gt;automatically resolve SAST findings when rules are disabled&lt;&#x2F;a&gt;, &lt;a href=&quot;#see-all-branch-related-settings-together&quot;&gt;a new view to see all branch-related settings together&lt;&#x2F;a&gt;, &lt;a href=&quot;#create-and-switch-branches-in-the-web-ide-beta&quot;&gt;the ability to create and switch branches in the Web IDE Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#compliance-frameworks-report&quot;&gt;compliance frameworks reports&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 115+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 170+ contributions they provided to GitLab 15.10! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.11 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_10&#x2F;15-10-cover-image-sm.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.9 released with new guest roles for viewing private repositories and license approval policies</title>
<release>15.9</release>
<link href='https://about.gitlab.com/releases/2023/02/22/gitlab-15-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/02/22/gitlab-15-9-released/</id>
<published>2023-02-22T00:00:00+00:00</published>
<author>
<name>Christen Dybenko</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.9 with &lt;a href=&quot;#users-with-the-guest-role-can-view-private-repositories&quot;&gt;guest roles viewing private repositories&lt;&#x2F;a&gt;, &lt;a href=&quot;#manage-license-approval-policies&quot;&gt;license approval policies&lt;&#x2F;a&gt; and &lt;a href=&quot;#new-license-compliance-scanner&quot;&gt;license compliance scanner&lt;&#x2F;a&gt;, &lt;a href=&quot;#notifications-now-available-in-the-gitlab-for-slack-app&quot;&gt;notifications in the GitLab for Slack app&lt;&#x2F;a&gt;,  &lt;a href=&quot;#code-suggestions-available-in-closed-beta&quot;&gt;code suggestions in closed beta&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 105+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 410+ contributions they provided to GitLab 15.9! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.10 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_9&#x2F;15_9-cover-image-sm.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.8 released with external status checks and self-managed SCIM</title>
<release>15.8</release>
<link href='https://about.gitlab.com/releases/2023/01/22/gitlab-15-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2023/01/22/gitlab-15-8-released/</id>
<published>2023-01-22T00:00:00+00:00</published>
<author>
<name>Hannah Sutor</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.8 with &lt;a href=&quot;#block-merges-unless-external-status-checks-pass&quot;&gt;block merges unless external status checks pass&lt;&#x2F;a&gt;, &lt;a href=&quot;#scim-support-for-self-managed-gitlab&quot;&gt;SCIM support for self-managed GitLab&lt;&#x2F;a&gt;, &lt;a href=&quot;#view-estimated-queuing-time-for-runners-in-the-admin-area&quot;&gt;view estimated queuing for runners in the admin area&lt;&#x2F;a&gt;, &lt;a href=&quot;#migrating-gitlab-projects-by-direct-transfer-beta&quot;&gt;migrate GitLab projects by direct transfer beta&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 35+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 85+ contributions they provided to GitLab 15.8! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.9 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_8&#x2F;15_8-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.7 released introducing the GitLab CLI and with browser-based DAST GA</title>
<release>15.7</release>
<link href='https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/</id>
<published>2022-12-22T00:00:00+00:00</published>
<author>
<name>Dilan Orrino</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;We are excited to announce the release of GitLab 15.7, which introduces the new &lt;a href=&quot;#introducing-the-gitlab-cli&quot;&gt;GitLab CLI&lt;&#x2F;a&gt;, &lt;a href=&quot;#browser-based-dast-general-availability&quot;&gt;general availability of browser-based DAST&lt;&#x2F;a&gt;, &lt;a href=&quot;#support-gitops-deployments-from-outside-the-default-branch&quot;&gt;support for GitOps deployments from outside the default branch&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 70+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 190+ contributions they provided to GitLab 15.7! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.8 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_7&#x2F;15_7-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.6 released with improvements to security policies, CI&#x2F;CD variables, and DAST API</title>
<release>15.6</release>
<link href='https://about.gitlab.com/releases/2022/11/22/gitlab-15-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/11/22/gitlab-15-6-released/</id>
<published>2022-11-22T00:00:00+00:00</published>
<author>
<name>Alana Bellucci</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.6 with
&lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;11&#x2F;22&#x2F;gitlab-15-6-released&#x2F;#git-abuse-rate-limiting&quot;&gt;Git abuse rate limiting&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;11&#x2F;22&#x2F;gitlab-15-6-released&#x2F;#support-for-special-characters-in-cicd-variables&quot;&gt;Support for special characters in CI&#x2F;CD variables&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;11&#x2F;22&#x2F;gitlab-15-6-released&#x2F;#group-and-subgroup-level-scan-result-policies&quot;&gt;group and subgroup-level scan result policies&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;11&#x2F;22&#x2F;gitlab-15-6-released&#x2F;#dast-api-analyzer-for-on-demand-dast-api-scans&quot;&gt;DAST API analyzer for on-demand DAST API scans&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 200+ contributions they provided to GitLab 15.6! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.7 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_6&#x2F;15_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.5 released with GitLab Cloud Seed and Autocomplete suggestions</title>
<release>15.5</release>
<link href='https://about.gitlab.com/releases/2022/10/22/gitlab-15-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/10/22/gitlab-15-5-released/</id>
<published>2022-10-22T00:00:00+00:00</published>
<author>
<name>Matt Wilson</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.5 with &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;10&#x2F;22&#x2F;gitlab-15-5-released&#x2F;#deploy-apps-to-google-cloud-with-gitlab-cloud-seed&quot;&gt;GitLab Cloud Seed&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;10&#x2F;22&#x2F;gitlab-15-5-released&#x2F;#autocomplete-suggestions-in-the-content-editor&quot;&gt;Autocomplete suggestions in the Content Editor&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;10&#x2F;22&#x2F;gitlab-15-5-released&#x2F;#error-tracking-open-beta&quot;&gt;Error Tracking Open Beta&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2022&#x2F;10&#x2F;22&#x2F;gitlab-15-5-released&#x2F;#operational-container-scanning&quot;&gt;Operational Container Scanning&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 50+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 153 contributions they provided to GitLab 15.5! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month&#x27;s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.6 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_5&#x2F;15_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.4 released with Suggested Reviewers and better VS Code CI&#x2F;CD experience</title>
<release>15.4</release>
<link href='https://about.gitlab.com/releases/2022/09/22/gitlab-15-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/09/22/gitlab-15-4-released/</id>
<published>2022-09-22T00:00:00+00:00</published>
<author>
<name>Derek Ferguson</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.4 with GitLab&#x27;s first machine learning powered feature: &lt;a href=&quot;#suggested-reviewers-open-beta&quot;&gt;Suggested Reviewers open beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#improved-cicd-integration-in-vs-code&quot;&gt;improved CI&#x2F;CD integration in VS Code&lt;&#x2F;a&gt;, &lt;a href=&quot;#getting-started-with-gitlab-pages-just-got-easier&quot;&gt;Pages Pipeline Wizard&lt;&#x2F;a&gt;, &lt;a href=&quot;#users-on-verified-domains-can-bypass-email-validation&quot;&gt;email validation bypass for verified domains&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 60+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 186 contributions they provided to GitLab 15.4! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.5 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_4&#x2F;15_4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.3 released with tasks for managing your work and free GitOps features</title>
<release>15.3</release>
<link href='https://about.gitlab.com/releases/2022/08/22/gitlab-15-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/08/22/gitlab-15-3-released/</id>
<published>2022-08-22T00:00:00+00:00</published>
<author>
<name>Amanda Rueda</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.3 with &lt;a href=&quot;#create-tasks-in-issues&quot;&gt;tasks in issues&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitops-features-are-now-free&quot;&gt;free GitOps features&lt;&#x2F;a&gt;, &lt;a href=&quot;#maintain-saml-group-links-with-api&quot;&gt;SAML group link API maintenance&lt;&#x2F;a&gt;, &lt;a href=&quot;#define-password-complexity-requirements&quot;&gt;advanced password complexity requirements&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 63 improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;We thank the wider GitLab community for the 348 contributions they provided to GitLab 15.3! At GitLab, everyone can contribute and we couldn&#x27;t have done it without you!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.4 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_3&#x2F;15_3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.2 released with live wiki diagram previews and redesigned merge request reports</title>
<release>15.2</release>
<link href='https://about.gitlab.com/releases/2022/07/22/gitlab-15-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/07/22/gitlab-15-2-released/</id>
<published>2022-07-22T00:00:00+00:00</published>
<author>
<name>Sam Kerr</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.2 with &lt;a href=&quot;#live-preview-diagrams-in-the-wiki-wysiwyg-editor&quot;&gt;Live preview diagrams in the wiki WYSIWYG editor&lt;&#x2F;a&gt;, &lt;a href=&quot;#incident-timeline&quot;&gt;Incident timelines&lt;&#x2F;a&gt;, &lt;a href=&quot;#group-and-subgroup-scan-execution-policies&quot;&gt;Group and subgroup scan execution policies&lt;&#x2F;a&gt;, &lt;a href=&quot;#change-failure-rate-chart-for-visualizing-software-stability&quot;&gt;Change failure rate chart for visualizing software stability&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.3 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_2&#x2F;15_2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.1 released with SAML Group Sync and SLSA level 2 build artifact attestation</title>
<release>15.1</release>
<link href='https://about.gitlab.com/releases/2022/06/22/gitlab-15-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/06/22/gitlab-15-1-released/</id>
<published>2022-06-22T00:00:00+00:00</published>
<author>
<name>Dov Hershkovitch</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.1 with &lt;a href=&quot;#saml-group-sync-for-self-managed-gitlab&quot;&gt;SAML Group Sync&lt;&#x2F;a&gt;, &lt;a href=&quot;#slsa-2-attestation-included-for-build-artifacts&quot;&gt;SLSA level 2 build artifact attestation&lt;&#x2F;a&gt;, &lt;a href=&quot;#link-to-included-cicd-configuration-from-the-pipeline-editor&quot;&gt;links to included CI&#x2F;CD configuration&lt;&#x2F;a&gt;, &lt;a href=&quot;#enhancing-visibility-into-value-stream-with-dora-metrics&quot;&gt;enhanced visibility into value stream with DORA metrics&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;Join us on June 23rd as we celebrate DevOps! GitLab co-founder and CEO, Sid Sijbrandij, will introduce best-selling author and DORA co-founder, Gene Kim. Gene will share his research and expectations for the future of DevOps then GitLab VP of Product, David DeSanto, will share how GitLab is evolving The One DevOps Platform to meet that future. We&#x27;ll also unveil a new program to support your career aspirations. You won&#x27;t want to miss this one-hour virtual event. &lt;a href=&quot;https:&#x2F;&#x2F;page.gitlab.com&#x2F;fifteen&quot;&gt;Reserve your seat&lt;&#x2F;a&gt; now!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.2 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_1&#x2F;15_1-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 15.0 released with WYSIWYG for Wiki, container scanning in all tiers</title>
<release>15.0</release>
<link href='https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-released/</id>
<published>2022-05-22T00:00:00+00:00</published>
<author>
<name>Kai Armstrong</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 15.0 with &lt;a href=&quot;#container-scanning-available-in-all-tiers&quot;&gt;container scanning in all tiers&lt;&#x2F;a&gt;, &lt;a href=&quot;#internal-notes&quot;&gt;internal notes&lt;&#x2F;a&gt;, &lt;a href=&quot;#link-external-organizations-and-contacts-to-issues&quot;&gt;better links to external organizations and contacts&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;Along with these exciting new features, there are a few &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-releases-15-breaking-changes&#x2F;&quot;&gt;breaking changes in 15.0&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Want to learn more about where we&#x27;re headed from Product leadership? Register now for the &lt;a href=&quot;https:&#x2F;&#x2F;page.gitlab.com&#x2F;fifteen&quot;&gt;GitLab 15 launch event&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.1 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;15_0&#x2F;15_0-cover-image.png&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.10 released with individual compliance violation reporting and a UI for streaming audit events</title>
<release>14.10</release>
<link href='https://about.gitlab.com/releases/2022/04/22/gitlab-14-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/04/22/gitlab-14-10-released/</id>
<published>2022-04-22T00:00:00+00:00</published>
<author>
<name>Brian Rhea</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 14.10 with &lt;a href=&quot;#compliance-report-individual-violation-reporting&quot;&gt;Compliance report individual violation reporting&lt;&#x2F;a&gt;, &lt;a href=&quot;#user-interface-for-streaming-audit-events&quot;&gt;a UI for streaming audit events&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-runner-operator-for-kubernetes&quot;&gt;GitLab Runner operator for Kubernetes&lt;&#x2F;a&gt;, &lt;a href=&quot;#escalating-manually-created-incidents&quot;&gt;escalating manually created incidents&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 15.0 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_10&#x2F;14_10-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.9 released with epic to epic linking and integrated security training</title>
<release>14.9</release>
<link href='https://about.gitlab.com/releases/2022/03/22/gitlab-14-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/03/22/gitlab-14-9-released/</id>
<published>2022-03-22T00:00:00+00:00</published>
<author>
<name>Brian Rhea</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 14.9 with &lt;a href=&quot;#link-an-epic-to-another-epic&quot;&gt;epic to epic linking&lt;&#x2F;a&gt;, &lt;a href=&quot;#integrated-security-training&quot;&gt;integrated security training&lt;&#x2F;a&gt;, &lt;a href=&quot;#new-design-for-the-environments-page&quot;&gt;a new Environments page design&lt;&#x2F;a&gt;, &lt;a href=&quot;#rule-mode-for-scan-result-policies&quot;&gt;rule mode for scan result policies&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.10 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_9&#x2F;14_9-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.8 released with new SSH key types and security approval policies</title>
<release>14.8</release>
<link href='https://about.gitlab.com/releases/2022/02/22/gitlab-14-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/02/22/gitlab-14-8-released/</id>
<published>2022-02-22T00:00:00+00:00</published>
<author>
<name>Brian Rhea</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 14.8 with &lt;a href=&quot;#support-for-ecdsa-sk-and-ed25519-sk-ssh-keys&quot;&gt;new SSH key types&lt;&#x2F;a&gt;, &lt;a href=&quot;#security-approval-policies&quot;&gt;security approval policies&lt;&#x2F;a&gt;, &lt;a href=&quot;#auto-completion-of-keywords-in-the-pipeline-editor&quot;&gt;pipeline editor autocomplete&lt;&#x2F;a&gt;, &lt;a href=&quot;#user-impersonation-audit-events-for-groups&quot;&gt;impersonation audit events&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.9 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_8&#x2F;14_8-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.7 released with Streaming Audit Events, GitLab Runner compliance with FIPS 140-2, and Group Access Tokens</title>
<release>14.7</release>
<link href='https://about.gitlab.com/releases/2022/01/22/gitlab-14-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2022/01/22/gitlab-14-7-released/</id>
<published>2022-01-22T00:00:00+00:00</published>
<author>
<name>Jensen Stava</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab 14.7 with &lt;a href=&quot;#streaming-audit-events&quot;&gt;Streaming Audit Events&lt;&#x2F;a&gt;, &lt;a href=&quot;#gitlab-runner-compliant-with-fips-140-2&quot;&gt;GitLab Runner compliance with FIPS 140-2&lt;&#x2F;a&gt;, &lt;a href=&quot;#group-access-tokens&quot;&gt;Group Access Tokens&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.8 release kickoff video.&lt;&#x2F;p&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_7&#x2F;14_7-cover-image.jpeg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.6 adds seamless Geo experience and supports .NET 6 in SAST</title>
<release>14.6</release>
<link href='https://about.gitlab.com/releases/2021/12/22/gitlab-14-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/12/22/gitlab-14-6-released/</id>
<published>2021-12-22T00:00:00+00:00</published>
<author>
<name>Viktor Nagy</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are thrilled to announce the release of GitLab 14.6, the last release for 2021. This release brings &lt;a href=&quot;#seamless-worldwide-performance-with-geo&quot;&gt;simplified Geo configuration&lt;&#x2F;a&gt; that helps globally distributed teams accelerate Git clone or Git pull commands by automatically using the geo site closest to them, an &lt;a href=&quot;#gitlab-agents-activity-information&quot;&gt;activity list for GitLab&#x27;s Agent&lt;&#x2F;a&gt; that logs real-time events such as connection and token status, and various SAST improvements including &lt;a href=&quot;#sast-scan-execution-policies&quot;&gt;SAST execution policies&lt;&#x2F;a&gt; and support for &lt;a href=&quot;#sast-support-for-net-6&quot;&gt;.NET 6&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 30+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.7 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_6&#x2F;14_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.5 released with infrastructure as code security scanning and group-level merge request approvals</title>
<release>14.5</release>
<link href='https://about.gitlab.com/releases/2021/11/22/gitlab-14-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/11/22/gitlab-14-5-released/</id>
<published>2021-11-22T00:00:00+00:00</published>
<author>
<name>Jackie Porter</name>
</author>
<content type='html'>&lt;p&gt;Today, we are thrilled to announce the release of GitLab 14.5 with &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2021&#x2F;11&#x2F;22&#x2F;gitlab-14-5-released&#x2F;#introducing-infrastructure-as-code-iac-security-scanning&quot;&gt;infrastructure as code security scanning&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2021&#x2F;11&#x2F;22&#x2F;gitlab-14-5-released&#x2F;#group-level-settings-for-merge-request-approvals&quot;&gt;group-level merge request approvals settings&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2021&#x2F;11&#x2F;22&#x2F;gitlab-14-5-released&#x2F;#gitlab-kubernetes-agent-available-in-gitlab-free&quot;&gt;Kubernetes Agent available in GitLab Free&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2021&#x2F;11&#x2F;22&#x2F;gitlab-14-5-released&#x2F;#explore-project-topics-tab&quot;&gt;project topics&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are only a selection of highlights from the 40+ improvements in this release. Read on to check out all of the super updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.6 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_5&#x2F;14_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.4 released with Scheduled DAST scans and Integrated error tracking</title>
<release>14.4</release>
<link href='https://about.gitlab.com/releases/2021/10/22/gitlab-14-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/10/22/gitlab-14-4-released/</id>
<published>2021-10-22T00:00:00+00:00</published>
<author>
<name>Orit Golowinski</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;Today, we are excited to announce the release of GitLab &lt;code&gt;14.4&lt;&#x2F;code&gt; with &lt;a href=&quot;#scheduled-dast-scans&quot;&gt;Scheduled DAST scans&lt;&#x2F;a&gt;, &lt;a href=&quot;#integrated-error-tracking-inside-gitlab-without-a-sentry-instance&quot;&gt;Integrated error tracking inside GitLab without a Sentry instance&lt;&#x2F;a&gt;, &lt;a href=&quot;#remote-repositories-for-gitlab-in-visual-studio-code&quot;&gt;Remote Repositories for GitLab in Visual Studio Code&lt;&#x2F;a&gt;, &lt;a href=&quot;#devops-adoption-trend-graph&quot;&gt;DevOps Adoption trend graph&lt;&#x2F;a&gt;, &lt;a href=&quot;#the-gitlab-operator-is-generally-available&quot;&gt;GA for GitLab Operator&lt;&#x2F;a&gt; and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the &lt;code&gt;30+&lt;&#x2F;code&gt; improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.5 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_4&#x2F;14_4-cover-image.jpeg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.3 releases Project Security Policies &amp; Next Gen SAST</title>
<release>14.3</release>
<link href='https://about.gitlab.com/releases/2021/09/22/gitlab-14-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/09/22/gitlab-14-3-released/</id>
<published>2021-09-22T00:00:00+00:00</published>
<author>
<name>Nicole Schwartz</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 14.3 with &lt;a href=&quot;#project-level-dast-and-secret-detection-scan-execution-policies&quot;&gt;project-level security scan execution policies&lt;&#x2F;a&gt;, &lt;a href=&quot;#next-generation-sast-to-reduce-ruby-false-positives&quot;&gt;next generation SAST to reduce Ruby false positives&lt;&#x2F;a&gt;, &lt;a href=&quot;#group-level-permissions-for-protected-environments&quot;&gt;group-level permissions for protected environments&lt;&#x2F;a&gt;, &lt;a href=&quot;#grant-group-access-to-the-gitlab-agents-cicd-tunnel&quot;&gt;group access for the GitLab Agent for Kubernetes&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.4 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_3&#x2F;14_3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.2 released with the Build Cloud for macOS beta and Markdown preview</title>
<release>14.2</release>
<link href='https://about.gitlab.com/releases/2021/08/22/gitlab-14-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/08/22/gitlab-14-2-released/</id>
<published>2021-08-22T00:00:00+00:00</published>
<author>
<name>Taylor McCaslin</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 14.2 with  &lt;a href=&quot;#gitlab-build-cloud-for-macos-beta&quot;&gt;introduction of the Build Cloud for macOS beta&lt;&#x2F;a&gt;, &lt;a href=&quot;#preview-markdown-live-while-editing&quot;&gt;Markdown preview&lt;&#x2F;a&gt;, &lt;a href=&quot;#launch-a-preconfigured-gitpod-workspace-from-a-merge-request&quot;&gt;expanded Gitpod integration&lt;&#x2F;a&gt;, &lt;a href=&quot;#track-use-of-dependency-scanning-and-fuzz-testing&quot;&gt;new DevOps adoption metrics&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights of the 50+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.3 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_2&#x2F;14_2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.1 released with Helm Chart Registry and Escalation Policies</title>
<release>14.1</release>
<link href='https://about.gitlab.com/releases/2021/07/22/gitlab-14-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/07/22/gitlab-14-1-released/</id>
<published>2021-07-22T00:00:00+00:00</published>
<author>
<name>Sam White</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to announce the release of GitLab 14.1 with the ability to &lt;a href=&quot;#build-publish-and-share-helm-charts&quot;&gt;build, publish, and share Helm charts&lt;&#x2F;a&gt;, &lt;a href=&quot;#escalation-policies&quot;&gt;create escalation policies to page responders&lt;&#x2F;a&gt;, &lt;a href=&quot;#cicd-tunnel-for-kubernetes-clusters&quot;&gt;connect GitLab Runners to your Kubernetes clusters&lt;&#x2F;a&gt;, &lt;a href=&quot;#code-coverage-merge-request-approval-rule&quot;&gt;enforce code coverage decisions&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the 50+ improvements in this release. Read on to check out all of the great updates below.&lt;&#x2F;p&gt;

&lt;p&gt;To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases page&lt;&#x2F;a&gt;, which includes our 14.2 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_1&#x2F;14_1-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 14.0 released with a celebration of GitLab 14</title>
<release>14.0</release>
<link href='https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/</id>
<published>2021-06-22T00:00:00+00:00</published>
<author>
<name>Darren Eastman</name>
</author>
<content type='html'>&lt;p&gt;When we think of everything released in the year since GitLab 13.0, we could not be more proud of our community and our team. This month, we celebrate our release of GitLab 14.0 by first taking a step back.&lt;&#x2F;p&gt;

&lt;p&gt;Together, we’ve made so much progress over the last year that we want to talk about everything it took to get to &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-14-modern-devops&#x2F;&quot;&gt;GitLab 14&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;We use semantic versioning so a point release, like 14.0, represents everything new in this month. GitLab 14 is the culmination of the past year. Even more than that, GitLab 14 represents the future of GitLab, and the future of DevOps.&lt;&#x2F;p&gt;

&lt;p&gt;With GitLab 14, teams of all sizes are moving from maintaining DIY DevOps toolchains to adopting modern DevOps. GitLab 14 is a complete DevOps platform with security embedded in its DNA, visibility and insights enabled by its single data store, and a seamless experience and extensible system, so end users and enterprises alike reap the benefits of speed and efficiency.&lt;&#x2F;p&gt;

&lt;p&gt;We’re so excited that we’ve written a post where you can &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-14-modern-devops&#x2F;&quot;&gt;read more about GitLab 14 and our vision for modern DevOps&lt;&#x2F;a&gt;, and how it enables any team to build and deliver software with velocity, visibility, and trust.&lt;&#x2F;p&gt;

&lt;p&gt;As ever, we are also excited about what’s new this month in 14.0. Read on for our regular highlights from dozens of significant new features and improvements. Along with these exciting new features, there are a few &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-moving-to-14-breaking-changes&#x2F;&quot;&gt;breaking changes in 14.0&lt;&#x2F;a&gt;. To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page, which includes our 14.1 release kickoff video.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;14_0&#x2F;14_0-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.12 released with On-Demand DAST and Deployment Frequency Chart</title>
<release>13.12</release>
<link href='https://about.gitlab.com/releases/2021/05/22/gitlab-13-12-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/05/22/gitlab-13-12-released/</id>
<published>2021-05-22T00:00:00+00:00</published>
<author>
<name>Mark Wood</name>
</author>
<content type='html'>&lt;p&gt;This month, we are excited to introduce usability and pipeline management improvements that strive to make your teams more productive, updates to make your deployments more secure, and insights to make your DevOps adoption more mature. These are just a few highlights from the &lt;strong&gt;44 improvements&lt;&#x2F;strong&gt; in this release.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;helping-you-manage-security-before-it-manages-you&quot;&gt;Helping you manage security before it manages you&lt;&#x2F;h2&gt;

&lt;p&gt;To ensure your production environment is always secure, &lt;a href=&quot;#on-demand-dast-ga-launch&quot;&gt;On-demand DAST scanning&lt;&#x2F;a&gt; is now generally available for all GitLab Ultimate customers. These on-demand scans will allow you to scan an already deployed application or API in any of your configured environments outside of a CI&#x2F;CD pipeline i.e., without requiring any code changes or merge requests to start a scan.&lt;&#x2F;p&gt;

&lt;p&gt;The &lt;a href=&quot;#semgrep-sast-analyzer-for-javascript-typescript-and-python&quot;&gt;Semgrep SAST analyzer&lt;&#x2F;a&gt; for JavaScript, TypeScript, and Python is also generally available. Semgrep&#x27;s flexible rule syntax is ideal for streamlining the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;sast&#x2F;#customize-rulesets&quot;&gt;GitLab Custom Rulesets&lt;&#x2F;a&gt; feature for extending and modifying detection rules, a popular request from GitLab SAST customers. It also allows GitLab customers access to Semgrep&#x27;s community rules. Thanks to the community contribution from &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;proletarius101&quot;&gt;@proletarius101&lt;&#x2F;a&gt;, we are also extending the &lt;a href=&quot;#mobile-application-binary-scanning-support&quot;&gt;Mobile Application Security Testing&lt;&#x2F;a&gt; to support &lt;code&gt;.ipa&lt;&#x2F;code&gt; (iOS) and &lt;code&gt;.apk&lt;&#x2F;code&gt; (Android) binary files, in addition to Xcode projects and Android manifest files that are already supported.&lt;&#x2F;p&gt;

&lt;p&gt;Many customers integrate their existing scanners into GitLab to benefit from a unified view. The Project Vulnerability Report now gives you the ability to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;229661&quot;&gt;filter by scanner and vendor&lt;&#x2F;a&gt;, allowing you to filter scan results for only third-party scanners or for all scanners including those from GitLab.&lt;&#x2F;p&gt;

&lt;p&gt;Application Security is a key focus area for GitLab for this year and your feedback is important to us. As the preference of web application development shifts rapidly towards building JavaScript-heavy and single-page applications, we have identified a need for a purpose built tool that provides more application testing coverage than a traditional proxy based crawler. We are inviting GitLab Ultimate customers to a public beta for a &lt;a href=&quot;#new-browser-based-crawler-for-dast-in-open-beta&quot;&gt;new browser-based crawler for DAST&lt;&#x2F;a&gt; which is expected to provide significantly better security testing coverage for these modern applications compared to our current proxy-based crawler.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;easier-pipeline-management-for-enhanced-usability&quot;&gt;Easier pipeline management for enhanced usability&lt;&#x2F;h2&gt;

&lt;p&gt;Pipelines are at the heart of our customers&#x27; CI&#x2F;CD success, and we want to make it easier to use for new and experienced users of GitLab. The pipeline editor will now come with a collapsible &lt;a href=&quot;#useful-gitlab-cicd-information-in-the-pipeline-editor&quot;&gt;panel of guided instructions&lt;&#x2F;a&gt; that will help new CI&#x2F;CD users create their first pipeline in a breeze.&lt;&#x2F;p&gt;

&lt;p&gt;For experienced CI&#x2F;CD users that require more flexibility in creating their pipelines, we are now supporting &lt;a href=&quot;#support-wildcards-when-including-yaml-cicd-configuration-files&quot;&gt;wildcards in the &lt;code&gt;include:&lt;&#x2F;code&gt; keyword&lt;&#x2F;a&gt; that will help you break your &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; file into multiple smaller files to improve reusability and readability. We also introduced the ability to &lt;a href=&quot;#support-variables-in-cicd-pipeline-workflowrules&quot;&gt;define variables within rules&lt;&#x2F;a&gt;, giving you the flexibility to set pipeline variables when certain conditions are met. Defining complex pipelines means there could be dependencies between jobs. The pipeline graph now &lt;a href=&quot;#show-job-dependencies-in-the-pipeline-graph&quot;&gt;shows dependencies between jobs&lt;&#x2F;a&gt;, which is helpful to visually track and understand the expected order in which the jobs will be run.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;insights-to-improve-your-devops-maturity&quot;&gt;Insights to improve your DevOps maturity&lt;&#x2F;h2&gt;

&lt;p&gt;You cannot fix what you cannot measure. In that spirit, we are continuing to natively support DORA4 metrics. We are happy to announce the introduction of a &lt;a href=&quot;#group-level-deployment-frequency-cicd-chart&quot;&gt;group-level deployment frequency chart&lt;&#x2F;a&gt;, which will help you understand the efficiency of your deployments over time, find bottlenecks, and focus on improvement areas that span across your projects and teams.&lt;&#x2F;p&gt;

&lt;p&gt;Value stream analytics help you identify inefficiencies and identify the root cause of those inefficiencies in your workflow. In 13.12, we have introduced &lt;a href=&quot;#view-and-sort-stage-items-in-a-value-stream&quot;&gt;pagination and sorting of workflow items&lt;&#x2F;a&gt;, which allows you to easily visualize and sort items in a specific stage to pinpoint bottlenecks. The &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;group&#x2F;value_stream_analytics&#x2F;#days-to-completion-chart&quot;&gt;Days to Completion chart&lt;&#x2F;a&gt; has been updated to show the &lt;a href=&quot;#view-average-time-to-complete-workflow-items&quot;&gt;average time to completion&lt;&#x2F;a&gt;, which helps identify meaningful trends over time.&lt;&#x2F;p&gt;

&lt;p&gt;In this release, thanks to the community contribution from &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;leetickett&quot;&gt;@leetickett&lt;&#x2F;a&gt;, we introduced the ability to view a &lt;a href=&quot;#time-tracking-reports-for-issues-and-merge-requests&quot;&gt;time tracking report&lt;&#x2F;a&gt; within an individual issue or merge request to provide visibility into how much time each contributor spent.&lt;&#x2F;p&gt;

&lt;p&gt;For many of our customers, merge requests are the central space for collaboration. We have introduced the ability to see &lt;a href=&quot;#code-quality-violation-notices-in-mr-diffs&quot;&gt;code quality violations&lt;&#x2F;a&gt; and &lt;a href=&quot;#failed-test-screenshots-in-test-report&quot;&gt;screenshots of failed tests&lt;&#x2F;a&gt; within the merge request to give you necessary context as a part of your normal workflow within GitLab.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-so-much-more&quot;&gt;And so much more!&lt;&#x2F;h2&gt;

&lt;p&gt;We continue to invest in improving the product usability in every release. Some of our favorite quality of life improvements in 13.12 include:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#users-group-counts-now-displayed-in-admin-area&quot;&gt;Users&#x27; group counts now displayed in Admin Area&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#elastic-stack-cluster-integration&quot;&gt;Bring your own Elastic Stack&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#create-incidents-via-api&quot;&gt;Create incidents via API&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#warn-administrator-when-removing-an-on-call-user&quot;&gt;Warn administrator when removing an on-call user&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#deleting-deploy-keys-will-inform-the-user-if-in-use&quot;&gt;Deleting deploy keys will inform the user if in use&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Read on for more features, performance enhancements and changes! To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page and our &lt;a href=&quot;https:&#x2F;&#x2F;youtube.com&#x2F;playlist?list=PL05JrBw4t0Krdajp3voZbcFVXk3O8JpPO&quot;&gt;14.0 release kickoff video&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_12&#x2F;13_12-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.11 released with Kubernetes Agent and Pipeline Compliance</title>
<release>13.11</release>
<link href='https://about.gitlab.com/releases/2021/04/22/gitlab-13-11-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/04/22/gitlab-13-11-released/</id>
<published>2021-04-22T00:00:00+00:00</published>
<author>
<name>Sarah Waldner</name>
</author>
<content type='html'>&lt;p&gt;On this Earth Day we are thinking about growth. Our customers are scaling their DevOps practices and with growth comes the need for even greater efficiencies and automated controls. The &lt;a href=&quot;#gitlab-agent-for-kubernetes-available-on-gitlabcom&quot;&gt;GitLab Agent for Kubernetes&lt;&#x2F;a&gt; is now available on GitLab.com to help you benefit from fast, pull-based deployments to your cluster, while GitLab.com manages the necessary server-side components of the Agent. &lt;a href=&quot;#compliance-pipeline-configurations&quot;&gt;Compliant Pipeline Configurations&lt;&#x2F;a&gt; let you define enforceable pipelines that will run for any project assigned a corresponding compliance framework, even &lt;a href=&quot;#create-custom-compliance-framework-labels&quot;&gt;custom ones&lt;&#x2F;a&gt;. We also have a host of features to improve pipeline efficiency and measurement, to provide &lt;a href=&quot;#on-call-schedule-management&quot;&gt;On-call Scheduling&lt;&#x2F;a&gt;, and even more security enhancements. These are just a few of the 50+ significant new features and improvements in this release.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;controls-to-help-you-grow-safely-and-efficiently&quot;&gt;Controls to help you grow safely and efficiently&lt;&#x2F;h2&gt;

&lt;p&gt;Controls can keep your automation on track as you grow and scale while simplifying compliance efforts. The &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;clusters&#x2F;agent&#x2F;&quot;&gt;GitLab Agent for Kubernetes&lt;&#x2F;a&gt; is core to GitLab&#x27;s Kubernetes integrations and is &lt;a href=&quot;#gitlab-kubernetes-agent-available-on-gitlabcom&quot;&gt;now available on GitLab.com&lt;&#x2F;a&gt;. The Agent-based integration supports pull-based deployments which are preferred by security and quickly becoming a popular method for Kubernetes deployment practices. The agent also supports Network Security policy integration and alerts which enables fine-tuned RBAC controls within your clusters. &lt;a href=&quot;#compliance-pipeline-configurations&quot;&gt;Compliant Pipeline Configurations&lt;&#x2F;a&gt; let you enforce a higher degree of separation of duties and reduce your business risks by defining enforceable pipelines that will run for any project assigned a corresponding compliance framework. At the same time, &lt;a href=&quot;#create-custom-compliance-framework-labels&quot;&gt;Custom Compliance Framework Labels&lt;&#x2F;a&gt; allow you to use your own requirements beyond the usual ones like PCI, HIPPA and such. The new &lt;a href=&quot;#re-authenticate-for-gitlab-administration-with-admin-mode&quot;&gt;Admin Mode&lt;&#x2F;a&gt; increases security and control of your GitLab instance by requiring admin users to reverify their credentials before running administrative commands. Audit reports are easier now too with a new &lt;a href=&quot;#export-a-user-access-report&quot;&gt;export&lt;&#x2F;a&gt; feature in your self-managed GitLab instance to see, all in one place, what groups, subgroups, and projects users have access to.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;speedier-pipelines&quot;&gt;Speedier pipelines&lt;&#x2F;h2&gt;

&lt;p&gt;“Speedy, reliable pipelines” is one of our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;ops&#x2F;#speedy-reliable-pipelines&quot;&gt;core product themes&lt;&#x2F;a&gt;, and we’ve delivered on that promise this month with a host of pipeline improvements.&lt;&#x2F;p&gt;

&lt;p&gt;The &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;pipeline_editor&#x2F;&quot;&gt;Pipeline Editor&lt;&#x2F;a&gt; helps you get to work even faster and stay more productive once you begin. The new &lt;a href=&quot;#create-initial-configuration-file-from-the-pipeline-editor&quot;&gt;Empty State&lt;&#x2F;a&gt; enhancement will allow new users to begin working with the pipeline editor on a new, blank pipeline file without having to create a config file first. The ability to configure &lt;a href=&quot;#use-multiple-caches-in-the-same-job&quot;&gt;multiple cache keys in a single job&lt;&#x2F;a&gt; will help you increase your pipeline performance and you can measure these improvements from the CI&#x2F;CD dashboard, where a &lt;a href=&quot;#track-dora-4-lead-time-for-changes-metric&quot;&gt;new DORA 4 graph&lt;&#x2F;a&gt; will show lead time for changes via time for code to be committed and deployed to production. As a related note, metrics on &lt;a href=&quot;#devops-adoption-metrics-available-at-the-group-level&quot;&gt;DevOps Adoption&lt;&#x2F;a&gt; are now available at the group level allowing users to understand how GitLab&#x27;s DevOps capabilities are being adopted.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;securing-your-software-supply-chain&quot;&gt;Securing your software supply chain&lt;&#x2F;h2&gt;

&lt;p&gt;Security pros will be happy to see the addition of the &lt;a href=&quot;#gitlab--semgrep-upgrading-sast-for-the-future&quot;&gt;Semgrep flexible rule syntax&lt;&#x2F;a&gt; to extend and modify custom detection rules, a popular request from GitLab SAST customers. We&#x27;ve also added support for &lt;a href=&quot;#support-for-custom-ca-certs-when-using-the-release-cli&quot;&gt;custom certificates&lt;&#x2F;a&gt; and &lt;a href=&quot;#ssh-key-expiration-email-notification&quot;&gt;email alerts for key expirations&lt;&#x2F;a&gt;. You can now improve your security posture by &lt;a href=&quot;#saml-enforcement-for-git-activity&quot;&gt;enforcing SAML for Git activity&lt;&#x2F;a&gt;. The new &lt;a href=&quot;#on-call-schedule-management&quot;&gt;On-call Schedule Management&lt;&#x2F;a&gt; routes alerts received in GitLab to the on-call engineer in the schedule for that project. This will be particularly helpful as we mature our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;software_supply_chain_security&#x2F;&quot;&gt;security alerts in the future&lt;&#x2F;a&gt;, providing a valuable incident management capability with end-to-end visibility across the entire DevOps process.&lt;&#x2F;p&gt;

&lt;p&gt;Read on for more features, performance enhancements and changes! To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page and our &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=5mTdhCuh9-I&quot;&gt;13.12 release kickoff&lt;&#x2F;a&gt; video.&lt;&#x2F;p&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_11&#x2F;13_11-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.10 released with Admin Enhancements and Vulnerability Management</title>
<release>13.10</release>
<link href='https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/03/22/gitlab-13-10-released/</id>
<published>2021-03-22T00:00:00+00:00</published>
<author>
<name>Christen Dybenko</name>
</author>
<content type='html'>&lt;p&gt;GitLab 13.10 is now available! This month, we’ve focused on scalability and manageability across the product so you can iterate and innovate faster, with greater security and fewer headaches. 13.10 offers administrative enhancements to help scale DevOps in your org, Geo package integrity verification to improve Disaster Recovery, vulnerability management automation to apply efficiency and consistency to security processes, and—as always—a ton of fantastic contributions from the wider community.  These are just a few of the &lt;strong&gt;40+ new features and improvements&lt;&#x2F;strong&gt; in this release.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;scaling-devops&quot;&gt;Scaling DevOps&lt;&#x2F;h2&gt;

&lt;p&gt;Managing a growing DevOps org is challenging. GitLab 13.10 introduces several new features to automate routine tasks, boost your efficiency, and grow DevOps  within the organization without losing control. We’ve leveled up support for DORA metrics with a new API to &lt;a href=&quot;#dora4-based-lead-time-for-changes&quot;&gt;track lead time for changes (via merge requests)&lt;&#x2F;a&gt; on the project level, as well as &lt;a href=&quot;#group-level-api-support-for-deployment-frequency&quot;&gt;Deployment Frequency metrics via API at the group level&lt;&#x2F;a&gt;, so you can track and identify blockers across a portfolio of projects.&lt;&#x2F;p&gt;

&lt;p&gt;When issues &lt;em&gt;do&lt;&#x2F;em&gt; arise, we&#x27;ve added tools to help you &lt;a href=&quot;#integrate-any-it-alerting-tool-with-gitlab&quot;&gt;integrate and manage alerts from multiple monitoring solutions&lt;&#x2F;a&gt;. 13.10 also enhances disaster recovery (DR) for customers using GitLab Geo by &lt;a href=&quot;#geo-verifies-replicated-package-files&quot;&gt;automatically verifying the data integrity of replicated Package Registries&lt;&#x2F;a&gt; and &lt;a href=&quot;#geo-supports-replicating-group-wikis&quot;&gt;replicating group wikis&lt;&#x2F;a&gt;. And finally, we&#x27;re extremely excited to announce &lt;a href=&quot;#gitlab-runner-for-red-hat-openshift-ga&quot;&gt;General Availability of GitLab Runner Operator on Red Hat OpenShift&lt;&#x2F;a&gt;, bringing GitLab to even more platforms!&lt;&#x2F;p&gt;

&lt;h2 id=&quot;scaling-vulnerability-management&quot;&gt;Scaling Vulnerability Management&lt;&#x2F;h2&gt;
&lt;p&gt;In 13.10, our security team has focused on reducing the overhead of managing and sharing vulnerabilities. &lt;a href=&quot;#vulnerability-bulk-status-updates&quot;&gt;Bulk Status Updates&lt;&#x2F;a&gt; allow security teams to modify the status of multiple vulnerabilities simultaneously. To help you identify and triage relevant information quickly, we&#x27;ve introduced &lt;a href=&quot;#clickable-file-and-line-number-links-on-vulnerability-report&quot;&gt;clickable file and line number links&lt;&#x2F;a&gt; in vulnerability reports that will deep-link you directly to relevant vulnerability details. We&#x27;ve also &lt;a href=&quot;#add-icons-to-the-vulnerability-trends-chart&quot;&gt;enhanced the interactivity of the vulnerability trends chart to make it easier to find and share information.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

&lt;h2 id=&quot;wider-community-contribution-highlights&quot;&gt;Wider community contribution highlights&lt;&#x2F;h2&gt;

&lt;p&gt;Every month we receive hundreds of contributions from the wider community, and in addition to &lt;a href=&quot;#mvp&quot;&gt;this month&#x27;s MVP&lt;&#x2F;a&gt;, we&#x27;d like to show our appreciation to a few of our many outstanding contributors.&lt;&#x2F;p&gt;

&lt;p&gt;Ongoing thanks to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;yo&quot;&gt;Yogi&lt;&#x2F;a&gt; for dozens of contributions to 13.10, as well as months of amazingly consistent contributions and throughput. You are an example of &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#iteration&quot;&gt;iteration&lt;&#x2F;a&gt; in action, and you continue to tackle challenges with &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#boring-solutions&quot;&gt;boring solutions&lt;&#x2F;a&gt; that deliver amazing results!&lt;&#x2F;p&gt;

&lt;p&gt;Thank you, &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;quatauta&quot;&gt;Daniel Schömer&lt;&#x2F;a&gt; for your iterations toward a &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;merge_requests&#x2F;56269#current-behavior-no-on-click-on-tap-expandcollapse&quot;&gt;more consistent UX in project settings&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;Thanks to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;haasef&quot;&gt;Felix Haase&lt;&#x2F;a&gt; for his work on &lt;a href=&quot;#clone-project-inside-visual-studio-code&quot;&gt;cloning projects from within Visual Studio Code&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;Thank you to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;KevSlashNull&quot;&gt;@KevSlashNull&lt;&#x2F;a&gt; for his work enabling &lt;a href=&quot;#open-project-in-visual-studio-code&quot;&gt;one-click opening of projects in VS Code&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;GitLab is a DevOps platform, and a huge reason for that is you. We&#x27;re a community, and in 13.10 alone we enjoyed &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.biterg.io&#x2F;goto&#x2F;937475d38035f496df3501c9b30af5ef&quot;&gt;over 250 merged wider community contributions&lt;&#x2F;a&gt;. Selecting one MVP wasn&#x27;t easy; thank you all for your professionalism and hard work.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-so-much-more&quot;&gt;And so much more!&lt;&#x2F;h2&gt;

&lt;p&gt;Some of our favorite quality of life improvements in 13.10 include:&lt;&#x2F;p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;papercuts.gitlab.com&#x2F;?milestone=13.10&quot;&gt;Dozens of quality of life usability improvements&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#search-and-autocomplete-by-full-name-in-comment-mentions&quot;&gt;Search for and autocomplete by full name in mentions in comments&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#automatically-retarget-merge-requests&quot;&gt;Automatically retarget merge requests&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#horizontal-navigation-for-value-stream-analytics&quot;&gt;Horizontal navigation for Value Stream Analytics&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Read on for more features, performance enhancements and changes! To preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page and our &lt;a href=&quot;https:&#x2F;&#x2F;youtu.be&#x2F;cVOkOTkQZ-A&quot;&gt;13.11 release kickoff video&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_10&#x2F;13_10-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.9 released with a Security Alert Dashboard and Maintenance Mode</title>
<release>13.9</release>
<link href='https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/</id>
<published>2021-02-22T00:00:00+00:00</published>
<author>
<name>Andrew Thomas</name>
</author>
<content type='html'>&lt;p&gt;GitLab 13.9 is now available to strengthen DevSecOps at scale, with a Security Alert Dashboard to triage high priority alerts, Maintenance Mode for unfailing support of distributed teams, better visibility including additional support for DORA metrics, and advanced automation capabilities that will help you deliver “better products, faster.” These are just a few of the &lt;strong&gt;60+ significant new features and improvements&lt;&#x2F;strong&gt; in this release.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;devsecops-at-scale&quot;&gt;DevSecOps at scale&lt;&#x2F;h2&gt;

&lt;p&gt;Keeping a production environment both secure and available are top priorities, but they can be difficult to balance. Our new &lt;a href=&quot;#security-alert-dashboard-for-container-network-policy-alerts&quot;&gt;Security Alert Dashboard&lt;&#x2F;a&gt; will help you balance security and reliability, by discerning between suspicious network activity that needs to be blocked immediately or that only needs further attention, minimizing disruption to users. We&#x27;re also excited to add &lt;a href=&quot;#javascript-and-python-support-for-coverage-guided-fuzz-testing&quot;&gt;JavaScript and Python support for coverage-guided fuzz testing&lt;&#x2F;a&gt;, making it easier to build secure and reliable software, with results piped into your Security Dashboard.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab is built for distributed teams. Our new &lt;a href=&quot;#maintenance-mode&quot;&gt;Maintenance Mode&lt;&#x2F;a&gt; enables read-only availability of your instance during more admin tasks, further reducing downtime. Scale and redundancy in data storage are improved with &lt;a href=&quot;#override-gitaly-cluster-replication-factor-for-specific-repositories&quot;&gt;variable Gitaly replication factors&lt;&#x2F;a&gt;, so you can tune your cluster to your own storage and budget constraints, while also enabling horizontal scaling.&lt;&#x2F;p&gt;

&lt;p&gt;Visibility is another core requirement in scaling DevOps, and &lt;a href=&quot;#release-analytics-at-the-group-level&quot;&gt;Release Analytics at the group level&lt;&#x2F;a&gt; continues to grow our support of DORA metrics, now aggregated for projects in a group. The &lt;a href=&quot;#easily-see-repeat-failed-tests-in-unit-test-reports&quot;&gt;new failed-test counter in Unit Test Reports&lt;&#x2F;a&gt; and a &lt;a href=&quot;#new-merge-request-metric-mean-time-to-merge&quot;&gt;new merge request metric, mean time to merge&lt;&#x2F;a&gt; help you achieve and understand underlying efficiencies.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;automate-your-way-to-better-products-faster&quot;&gt;Automate your way to better products, faster&lt;&#x2F;h2&gt;

&lt;p&gt;If you’re new to DevOps or renewing stalled efforts, an edict to deliver “better products, faster” can sound a little like “doing more, with less;” it may feel counterintuitive. But DevOps is the answer and automation is the key to doing both well.&lt;&#x2F;p&gt;

&lt;p&gt;One sure way to build and test faster is to look for redundancies in configuration. A new function in 13.9 saves you time by enabling &lt;a href=&quot;#select-cicd-configuration-from-any-job-and-reuse-it&quot;&gt;reuse in your pipeline of a CI&#x2F;CD configuration from any job&lt;&#x2F;a&gt;, even if it&#x27;s in another file.&lt;&#x2F;p&gt;

&lt;p&gt;Automating at scale often requires mitigating complexity. When you’ve broken down your pipeline configuration into many files, you’ll like that you can now &lt;a href=&quot;#view-an-expanded-version-of-the-cicd-configuration&quot;&gt;view an expanded version of the configuration&lt;&#x2F;a&gt;. Deployment processes using parent-child or multi-project pipelines can also now use &lt;a href=&quot;#resource-group-for-multi-project-and-parent-child-pipelines&quot;&gt;resource groups to manage concurrency across stages, jobs, and even projects&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;wider-community-contribution-highlights&quot;&gt;Wider community contribution highlights&lt;&#x2F;h2&gt;

&lt;p&gt;We’re thrilled to introduce &lt;a href=&quot;#gpu-and-smart-scheduling-support-for-gitlab-runner&quot;&gt;GPU and smart scheduling support for GitLab Runner&lt;&#x2F;a&gt;, supporting specialized compute workloads like those in machine learning, and contributed by &lt;a href=&quot;#mvp&quot;&gt;this month&#x27;s MVP, Andreas Gravgaard Andersen&lt;&#x2F;a&gt;! Andreas showed awesome perseverance through reviews that spanned 10 months.&lt;&#x2F;p&gt;

&lt;p&gt;Thanks to another brilliant contribution, you can now &lt;a href=&quot;#follow-user-activity&quot;&gt;follow other GitLab users’ activity&lt;&#x2F;a&gt;! You might start by following its contributor, &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;bufferoverflow&quot;&gt;Roger Meier @bufferoverflow&lt;&#x2F;a&gt; from &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;siemens&quot;&gt;Siemens&lt;&#x2F;a&gt;, himself a &lt;a href=&quot;https:&#x2F;&#x2F;contributors.gitlab.com&#x2F;docs&#x2F;notable-contributors&quot;&gt;GitLab Hall of Famer&lt;&#x2F;a&gt; and sage of Open Source and InnerSource.&lt;&#x2F;p&gt;

&lt;p&gt;Thank you to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;marshall007&quot;&gt;Marshall Cottrell @marshall007 from NASA&lt;&#x2F;a&gt; for &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;cluster-integration&#x2F;gitlab-agent&#x2F;-&#x2F;merge_requests&#x2F;281#note_507445139&quot;&gt;creating a 1-liner installer for the GitLab Agent for Kubernetes&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;charts&#x2F;gitlab&#x2F;-&#x2F;merge_requests&#x2F;1807#note_505567583&quot;&gt;simplifying its configuration&lt;&#x2F;a&gt;, enabling users to get started with the Agent much more easily. Marshall&#x27;s feedback, ideas, and collaboration beyond merged contributions were also called &quot;invaluable.&quot;&lt;&#x2F;p&gt;

&lt;p&gt;Thank you to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;KevSlashNull&quot;&gt;Kev @KevSlashNull&lt;&#x2F;a&gt; of SiegeGG, who &lt;a href=&quot;#vulnerability-report-activity-filter&quot;&gt;added an Activity filter to Vulnerability Reports&lt;&#x2F;a&gt;, helping you drill into precisely the vulnerability list view you need. GitLab&#x27;s own AppSec team are grateful as are many others, for this and Kev&#x27;s many contributions.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab isn&#x27;t only a &lt;a href=&quot;&#x2F;solutions&#x2F;devops-platform&#x2F;&quot;&gt;DevOps platform&lt;&#x2F;a&gt;, or a company, we&#x27;re also a community, and in 13.9 alone we enjoyed an incredible &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.biterg.io&#x2F;goto&#x2F;937475d38035f496df3501c9b30af5ef&quot;&gt;299 merged wider community contributions&lt;&#x2F;a&gt;. Selecting one MVP wasn&#x27;t easy; thank you all for your professionalism and hard work.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-so-much-more&quot;&gt;And so much more!&lt;&#x2F;h2&gt;

&lt;p&gt;Some of our favorite quality of life improvements in 13.9 include:&lt;&#x2F;p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#create-changelogs-using-the-gitlab-api&quot;&gt;Create changelogs using the GitLab API&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#mark-changes-as-viewed-in-merge-requests&quot;&gt;Mark changes as viewed in merge requests&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#request-a-follow-up-review-from-a-reviewer&quot;&gt;Request a follow-up review from a Reviewer&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#create-jira-issues-from-vulnerabilities&quot;&gt;Create Jira issues from Vulnerabilities&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#assign-incidents-to-milestones&quot;&gt;Assign incidents to milestones&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#markdown-links-for-feature-flags&quot;&gt;Markdown links for Feature Flags&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#allow-deploy-keys-to-push-to-protected-branches&quot;&gt;Allow Deploy Keys to push to protected branches&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Read on for more, and to preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page and our &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=8VolMk8VorM&quot;&gt;13.10 release kickoff video&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_9&#x2F;13_9-cover-image-2.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.8 released with a Pipeline Editor and DORA metrics</title>
<release>13.8</release>
<link href='https://about.gitlab.com/releases/2021/01/22/gitlab-13-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2021/01/22/gitlab-13-8-released/</id>
<published>2021-01-22T00:00:00+00:00</published>
<author>
<name>Farnoosh Seifoddini</name>
</author>
<content type='html'>&lt;p&gt;Today, we are excited to introduce a dedicated Pipeline Editor, a deployment frequency dashboard, and several quality of life improvements that will make using GitLab every day even more enjoyable. These are just a few highlights from the 50+ improvements in this release.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;the-new-pipeline-editor-makes-cicd-easy-to-use&quot;&gt;The new Pipeline Editor makes CI&#x2F;CD easy to use&lt;&#x2F;h2&gt;

&lt;p&gt;Since its inception, the defining feature of GitLab CI&#x2F;CD has been the &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; configuration file. Configuring pipelines as code means you can version control and collaborate on pipelines using the same interfaces you use for your application code. Additionally, GitLab&#x27;s advanced syntax provides a high degree of customization for sophisticated and demanding CI&#x2F;CD use cases. However, all of this power and flexibility comes with a fair bit of complexity. This is why our &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;epics&#x2F;4534&quot;&gt;vision for CI&#x2F;CD&lt;&#x2F;a&gt; is to create a visual pipeline authoring experience, built-in to GitLab, that simplifies the complexity letting you quickly create and edit pipelines while still exposing advanced options when you need them.&lt;&#x2F;p&gt;

&lt;p&gt;Today, we’re pleased to introduce the first iteration of the &lt;a href=&quot;#pipeline-editor&quot;&gt;Pipeline Editor&lt;&#x2F;a&gt;. Starting in 13.8, you&#x27;ll have a dedicated editor designed for CI&#x2F;CD with some enhanced functionality such as built-in &lt;a href=&quot;#ci-lint-tool-in-the-pipeline-editor-page&quot;&gt;linting&lt;&#x2F;a&gt; and &lt;a href=&quot;#cicd-configuration-validation-in-pipeline-editor&quot;&gt;configuration validation&lt;&#x2F;a&gt;. A &lt;a href=&quot;#visualization-of-pipeline-configuration&quot;&gt;pipeline visualizer&lt;&#x2F;a&gt; in the editor will show you what your pipelines will look like before you commit your changes. These capabilities allow new users to get started with GitLab CI&#x2F;CD quickly and make experienced power users more efficient. This is just the beginning of what&#x27;s in store for the Pipeline Editor. We can&#x27;t wait for you to try it out so you can share your feedback, suggestions, and code contributions.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;improve-your-devops-maturity-with-deployment-frequency-metrics&quot;&gt;Improve your DevOps maturity with deployment frequency metrics&lt;&#x2F;h2&gt;

&lt;p&gt;IT leaders and practitioners alike love DevOps. Developers and software engineers love that DevOps makes their job easier while IT leaders love that DevOps makes the business perform better. For several years, &lt;a href=&quot;https:&#x2F;&#x2F;www.devops-research.com&#x2F;research.html&quot;&gt;DORA, the DevOps Research and Assessment firm&lt;&#x2F;a&gt;, has conducted primary research on the impact of DevOps in the enterprise. Their &lt;a href=&quot;https:&#x2F;&#x2F;www.devops-research.com&#x2F;research.html#reports&quot;&gt;published results&lt;&#x2F;a&gt; have shown that DevOps maturity leads to positive business outcomes like happier customers, greater market share, and increased revenue. Four metrics in particular, commonly known as the “DORA 4”, are highly correlated with business performance. These are deployment frequency, lead time for changes, time to restore service, and change failure rate.&lt;&#x2F;p&gt;

&lt;p&gt;We’ve heard from many of you that you want to measure these metrics so that you can improve them. However, instrumenting your systems to capture and report on these metrics can be difficult and time-consuming. We decided to build them into GitLab for you so you can focus on improving your DevOps maturity instead of instrumentation. Starting with GitLab 13.8 you can find &lt;a href=&quot;#deployment-frequency-charts&quot;&gt;deployment frequency charts&lt;&#x2F;a&gt; in your CI&#x2F;CD analytics. This is just the first of the DORA 4 metrics to come to GitLab. Our &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;epics&#x2F;4358&quot;&gt;vision for the coming year&lt;&#x2F;a&gt; will be to add the additional three metrics so you’ll be able to measure and optimize your DevOps practices.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;a-few-small-features-to-improve-your-quality-of-life&quot;&gt;A few small features to improve your quality of life&lt;&#x2F;h2&gt;

&lt;p&gt;As GitLab gets better with every iteration sometimes the most exciting improvements aren’t the big new features, but the small UX improvements that take a tedious task and make it simple and easy. In this release, we’ve shipped several long-asked-for enhancements that we think you’ll enjoy such as the ability to:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#send-an-email-to-an-issue&quot;&gt;Send an email to an issue&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#click-and-drag-multiline-merge-request-comments&quot;&gt;Click and drag to make multi-line comments&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#download-artifacts-directly-from-the-merge-request-widget&quot;&gt;Download artifacts from an MR widget&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#repeat-failed-test-counter&quot;&gt;Identify flaky tests with a repeat failed test counter&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#rebase-quick-action-for-merge-requests&quot;&gt;Rebase an MR branch with a quick action&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;These are just a few of many ways GitLab has been made better in this release. Read on to see more. And, if you&#x27;d like to preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page as well as our &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=NYX-thYThCo&quot;&gt;13.9 release kick-off video&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_8&#x2F;13_8-cover-image-2.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.7 released with merge request reviewers and automatic rollback upon failure</title>
<release>13.7</release>
<link href='https://about.gitlab.com/releases/2020/12/22/gitlab-13-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/12/22/gitlab-13-7-released/</id>
<published>2020-12-22T00:00:00+00:00</published>
<author>
<name>Michael Karampalas</name>
</author>
<content type='html'>&lt;p&gt;What a year 2020 has been! We&#x27;re excited to share what&#x27;s new in 13.7 with over &lt;strong&gt;45&lt;&#x2F;strong&gt; features and improvements shipping just in time for the holidays!&lt;&#x2F;p&gt;

&lt;p&gt;On behalf of everyone at GitLab, I want to take a second to thank everyone in our community for your contributions and the positive impact you&#x27;ve made. Without you, GitLab would not be what it is today.&lt;&#x2F;p&gt;

&lt;p&gt;Here&#x27;s to you and all of our team members that helped make 2020 an incredible year despite the adversity and unprecedented times. Please continue staying safe, happy, and healthy this holiday season.&lt;&#x2F;p&gt;

&lt;p&gt;Here&#x27;s what you can look forward to in 13.7:&lt;&#x2F;p&gt;

&lt;h2 id=&quot;enhanced-project-management-for-cross-collaboration&quot;&gt;Enhanced project management for cross-collaboration&lt;&#x2F;h2&gt;

&lt;p&gt;Merge Requests (MRs) are crucial to foster cross-collaboration and can be directly linked to relevant issues, providing a central location to communicate via comments, suggest code changes, perform code reviews, and much more. In this release, we&#x27;ve added &lt;a href=&quot;#reviewers-for-merge-requests&quot;&gt;merge request reviewers&lt;&#x2F;a&gt;, a capability to improve the code review process by making reviews easier and more organized. Now you&#x27;ll be able to quickly find out who&#x27;s involved in the merge request or request a formal review that will send them a notification.&lt;&#x2F;p&gt;

&lt;p&gt;Context switching and manual tasks in your workflow hinder your ability to efficiently collaborate across groups and projects. It means you spend less time developing valuable features and more time managing your projects, which is why the ability to &lt;a href=&quot;#clone-an-issue-with-a-quick-action&quot;&gt;clone issues with quick actions&lt;&#x2F;a&gt; is so valuable for you to streamline agile planning and project management.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#collaboration&quot;&gt;Collaborating&lt;&#x2F;a&gt; on projects and &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#iteration&quot;&gt;iterating&lt;&#x2F;a&gt; rapidly to develop your applications means you need to be able to quickly determine the order of importance of your issues, identify any blockers, and use that information to prioritize what you&#x27;ll work on next. Now, you can &lt;a href=&quot;#sort-issues-by-the-number-of-issues-they-are-blocking&quot;&gt;sort issues by blockers&lt;&#x2F;a&gt; to quickly find out which of your issues are blocking progress for other issues, as well as easily sort by the number of blockers in your issue list.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;improved-release-automation-and-deployment-flexibility&quot;&gt;Improved release automation and deployment flexibility&lt;&#x2F;h2&gt;

&lt;p&gt;You need flexibility to control how you orchestrate, automate, and deploy your applications on a regular basis. Deploying your applications reliably and frequently gets value into the hands of your customers sooner.&lt;&#x2F;p&gt;

&lt;p&gt;To improve how GitLab automates releases, we&#x27;ve added &lt;a href=&quot;#auto-rollback-in-case-of-failure&quot;&gt;automatic rollback in case of failure&lt;&#x2F;a&gt;. This feature automatically reverts an unsuccessful deployment back to the last successful deployment and sends an automatic notification to alert you of the status. You won&#x27;t have to manually make any changes and can be confident that potential problems won&#x27;t cause downtime or intensify while you work towards a fix.&lt;&#x2F;p&gt;

&lt;p&gt;An improvement that goes well with automatic rollback in the event of a failure is the ability to &lt;a href=&quot;#show-deployment-status-on-the-environments-page&quot;&gt;see the deployment status in the Environment page&lt;&#x2F;a&gt;. Now you can easily find deployment statuses and identify what actions you need to take, such as stopping or rolling back a deployment.&lt;&#x2F;p&gt;

&lt;p&gt;We&#x27;ve also shipped the first officially supported beta of &lt;a href=&quot;#gitlab-runner-for-red-hat-openshift&quot;&gt;GitLab Runner container on Red Hat OpenShift and our Certified Runner Operator&lt;&#x2F;a&gt; to give you more flexibility over how you release with GitLab. We&#x27;re working to make this generally available soon, so stay tuned for more information in future releases.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;more-reliable-and-efficient-package-and-dependency-management&quot;&gt;More reliable and efficient package and dependency management&lt;&#x2F;h2&gt;

&lt;p&gt;Your workflow depends on a wide variety of programming languages, binaries, integrations, and artifacts that are all important inputs or outputs as a result of your development process. The more efficiently you can manage your packages and dependencies, the less development time goes to waste, and with efficiency in mind, we&#x27;ve added the option to &lt;a href=&quot;#quickly-find-and-view-generic-packages&quot;&gt;quickly find and view generic packages&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;We&#x27;ve also made improvements to GitLab&#x27;s Dependency Proxy, which, by the way, was made &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;minor-breaking-change-dependency-proxy&#x2F;&quot;&gt;available in Core&lt;&#x2F;a&gt; in GitLab 13.6.&lt;&#x2F;p&gt;

&lt;p&gt;You can now &lt;a href=&quot;#avoid-docker-rate-limits-and-speed-up-your-pipelines&quot;&gt;avoid Docker rate-limits and speed up your pipelines with the Dependency Proxy&lt;&#x2F;a&gt; to assure confidence in reliability and improve efficiency when caching your container images hosted on DockerHub.&lt;&#x2F;p&gt;

&lt;p&gt;Another improvement that many of you in the community were anticipating, the &lt;a href=&quot;#use-the-dependency-proxy-with-private-projects&quot;&gt;Dependency Proxy now works with private projects&lt;&#x2F;a&gt; and addresses the limitations that prevented those of you with private projects from taking advantage of this feature.&lt;&#x2F;p&gt;

&lt;p&gt;Last but not least, you&#x27;ll be able to &lt;a href=&quot;#use-pre-defined-variables-with-the-dependency-proxy&quot;&gt;use pre-defined variables with the Dependency Proxy&lt;&#x2F;a&gt; instead of relying on your own defined variables or hard-coding values in your &lt;code&gt;gitlab.ci-yml&lt;&#x2F;code&gt; file. This provides a more scalable and efficient way to get started proxying and caching images.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-more&quot;&gt;And more&lt;&#x2F;h2&gt;

&lt;p&gt;Check out a few other awesome features shipping in 13.7 below:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#import-requirements-from-external-tools&quot;&gt;Import requirements from a CSV file&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#saml-user-provisioning-for-gitlabcom&quot;&gt;SAML user provisioning&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#set-deployment-traffic-weight-via-the-ui&quot;&gt;Set deployment traffic weight via UI&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#api-support-for-deployment-frequency&quot;&gt;API support for Deployment Frequency&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;These are just a few highlights out of many new features and performance improvements. If you&#x27;d like to preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page as well as our &lt;a href=&quot;https:&#x2F;&#x2F;youtu.be&#x2F;bWKdW-s9o9E&quot;&gt;13.8 release kick off video&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_7&#x2F;13_7-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.6 released with Auto Deploy to EC2 and Usage Trends Dashboard </title>
<release>13.6</release>
<link href='https://about.gitlab.com/releases/2020/11/22/gitlab-13-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/11/22/gitlab-13-6-released/</id>
<published>2020-11-22T00:00:00+00:00</published>
<author>
<name>James Heimbuck</name>
</author>
<content type='html'>&lt;p&gt;At GitLab, we are focused on improving developer productivity and satisfaction. And GitLab 13.6 has all the right ingredients to help you achieve all that and more! We hope that you find these top features, and the &lt;strong&gt;60+ new features and improvements&lt;&#x2F;strong&gt; packed in this release, useful.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;improved-ease-of-use-and-automation-for-efficiency&quot;&gt;Improved ease of use and automation for efficiency&lt;&#x2F;h2&gt;

&lt;p&gt;To make it easy for you to get started with GitLab CI&#x2F;CD with Amazon Web Services (AWS), Auto DevOps has now been extended to support AWS, so you can now &lt;a href=&quot;#auto-deploy-to-ec2&quot;&gt;Auto-Deploy to Amazon EC2&lt;&#x2F;a&gt; using Auto DevOps without using Kubernetes (as previously required by Auto DevOps).&lt;&#x2F;p&gt;

&lt;p&gt;Docker Hub has enforced rate limits on &lt;code&gt;docker pull&lt;&#x2F;code&gt; requests. We have &lt;a href=&quot;&#x2F;blog&#x2F;mitigating-the-impact-of-docker-hub-pull-requests-limits&#x2F;&quot;&gt;mitigated the impact&lt;&#x2F;a&gt; for our SaaS and self-managed users and have shared ways to &lt;a href=&quot;&#x2F;blog&#x2F;docker-hub-rate-limit-monitoring&#x2F;&quot;&gt;monitor the limits with Prometheus&lt;&#x2F;a&gt; in your environments. We want all our users to stay safe with their CI&#x2F;CD pipelines and Kubernetes clusters. We are moving the &lt;a href=&quot;#the-dependency-proxy-is-now-open-source&quot;&gt;Dependency Proxy&lt;&#x2F;a&gt; to Core available for everyone.&lt;&#x2F;p&gt;

&lt;p&gt;Listening to the community’s feedback to have a more descriptive default branch, Group owners now have more flexibility in configuring a custom &lt;a href=&quot;#customize-the-initial-branch-name-for-new-projects-within-a-group&quot;&gt;default initial branch name for new repositories&lt;&#x2F;a&gt; as opposed to the &lt;code&gt;master&lt;&#x2F;code&gt; branch. Speaking of defaults, the Static Site Editor can use a &lt;a href=&quot;#merge-request-templates-for-static-site-editor-changes&quot;&gt;default merge request template&lt;&#x2F;a&gt; across a project, reducing the need to navigate to the merge request after submission to update the description.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;improved-visibility-for-faster-decision-making&quot;&gt;Improved visibility for faster decision making&lt;&#x2F;h2&gt;

&lt;p&gt;You cannot fix what you cannot find. With 13.6, we’ve made improvements to several dashboards and reports to aid you with faster decision making.&lt;&#x2F;p&gt;

&lt;p&gt;With the &lt;a href=&quot;#display-code-quality-severity-ratings&quot;&gt;code quality severity&lt;&#x2F;a&gt; included within the merge request and the &lt;a href=&quot;#generate-html-reports-for-code-quality&quot;&gt;Full Code Quality Report&lt;&#x2F;a&gt;, you can now quickly determine which code quality violations are critical to resolve before merging. Thanks for the community contribution with Code Quality Report, &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;vicken.papaya&quot;&gt;Vicken Simonian&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;We’ve made updates to the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;security_dashboard&#x2F;#project-security-dashboard&quot;&gt;Project Security Dashboard&lt;&#x2F;a&gt; to include the &lt;a href=&quot;#pipeline-status-in-project-security-dashboard&quot;&gt;results of the latest run pipeline security scan&lt;&#x2F;a&gt; and also a &lt;a href=&quot;#new-vulnerability-trends-chart&quot;&gt;dynamic vulnerability trend chart&lt;&#x2F;a&gt; to help you stay on top of the real time and historical vulnerability trends. We&#x27;ve also added the &lt;a href=&quot;#coverage-guided-fuzz-testing-artifacts-available-in-merge-request-widget&quot;&gt;fuzz testing results in the merge request&lt;&#x2F;a&gt; along with the other security results and improved the readability of this report by adding the source file name and line number to help you quickly find the exact crash location and fix it.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab Self Managed Administrators can &lt;a href=&quot;#visualize-users-projects-groups-issues-mrs-and-pipeline-activity&quot;&gt;now see their organization&#x27;s usage trends&lt;&#x2F;a&gt; for popular features such as users, projects, groups, issues, and pipelines over the last 12 months.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;improved-extensibility-for-a-seamless-workflow&quot;&gt;Improved extensibility for a seamless workflow&lt;&#x2F;h2&gt;

&lt;p&gt;We aim to &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;product&#x2F;categories&#x2F;gitlab-the-product&#x2F;#plays-well-with-others&quot;&gt;play well with other popular tools&lt;&#x2F;a&gt; you may be using in your environment so that you have a seamless experience, even when you use only a few parts of GitLab. With 13.6, to enable easy access and collaboration from within VS Code, we’ve improved our &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;#gitlab-workflow---vs-code-extension&quot;&gt;extension with VS Code&lt;&#x2F;a&gt; to &lt;a href=&quot;#insert-gitlab-snippets-directly-in-vs-code&quot;&gt;insert Snippets&lt;&#x2F;a&gt;, view and comment on merge requests and issues directly from VS Code rather than switching to the GitLab interface.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab &lt;a href=&quot;#group-level-management-of-project-integrations&quot;&gt;integrations&lt;&#x2F;a&gt; can now be configured at a group level in addition to instance and project level - helping group owners manage integrations with ease.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-more&quot;&gt;And more&lt;&#x2F;h2&gt;

&lt;p&gt;To enable you to grow beyond the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;10GB per project storage limit&lt;&#x2F;a&gt;, we recently introduced an add-on to &lt;a href=&quot;https:&#x2F;&#x2F;customers.gitlab.com&#x2F;&quot;&gt;purchase additional storage&lt;&#x2F;a&gt; for your group or personal name space. In addition to &lt;a href=&quot;#the-dependency-proxy-is-now-open-source&quot;&gt;Dependency Proxy&lt;&#x2F;a&gt;, we&#x27;ve also moved &lt;a href=&quot;#tracing-has-been-moved-to-core&quot;&gt;Tracing&lt;&#x2F;a&gt; to Core as part of this release.&lt;&#x2F;p&gt;

&lt;p&gt;These are just a few highlights from the many new features and performance improvements described below. If you&#x27;d like to preview what&#x27;s coming in next month’s release, check out our &lt;a href=&quot;&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page as well as our &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;playlist?list=PL05JrBw4t0KoDQr8x2MaumyU7d8_6icNH&quot;&gt;13.7 release kick off&lt;&#x2F;a&gt; video series where the Product Managers highlight key features coming in the next release.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_6&#x2F;13_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.5 released with Mobile App Sec, Group Wikis, and more!</title>
<release>13.5</release>
<link href='https://about.gitlab.com/releases/2020/10/22/gitlab-13-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/10/22/gitlab-13-5-released/</id>
<published>2020-10-22T00:00:00+00:00</published>
<author>
<name>Thao Yeager</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;One of GitLab’s core values is &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#collaboration&quot;&gt;collaboration&lt;&#x2F;a&gt; and it&#x27;s a key part of DevOps. This month we have several features aimed at collaboration among your team, across your tools, and with your peers as part of the &lt;strong&gt;60 improvements&lt;&#x2F;strong&gt; packed into this release.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;mobile-application-security-scanning&quot;&gt;Mobile application security scanning&lt;&#x2F;h2&gt;

&lt;p&gt;Community contributions are one of the best kinds of collaboration! One of our customers embraced our security scanning capabilities to &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;solutions&#x2F;security-compliance&#x2F;&quot;&gt;shift left&lt;&#x2F;a&gt; and empower developers to find and fix security flaws, yet they also wanted the same abilities for iOS and Android mobile applications. Using our &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;development&#x2F;integrations&#x2F;secure.html&quot;&gt;integration guidance&lt;&#x2F;a&gt;, they brought MobSF into the merge request pipeline and the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;security_dashboard&#x2F;&quot;&gt;security dashboards&lt;&#x2F;a&gt; alongside SAST and all the other &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;&quot;&gt;GitLab security scan&lt;&#x2F;a&gt; results.&lt;&#x2F;p&gt;

&lt;p&gt;For their contribution, Brian Williams and the H-E-B Digital team are this month’s &lt;a href=&quot;#mvp&quot;&gt;MVP&lt;&#x2F;a&gt;. This new Mobile SAST language coverage, combined with our existing &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;coverage_fuzzing&#x2F;&quot;&gt;fuzz testing&lt;&#x2F;a&gt; for Swift and Java projects, now offers a valuable security testing solution for mobile apps.&lt;&#x2F;p&gt;

&lt;p&gt;Giving works both ways. Therefore, we have officially finished &lt;a href=&quot;#feature-flags-made-available-in-all-tiers&quot;&gt;moving Feature flags to core&lt;&#x2F;a&gt;, open-sourcing it for greater community engagement. This completes one more step of our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;new-features-to-core&#x2F;&quot;&gt;plan to move 18 features to Core&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;group-wikis-and-more&quot;&gt;Group wikis and more!&lt;&#x2F;h2&gt;

&lt;p&gt;Groups collaborate in many ways and we now offer a few more ways to do so. A feature long sought after is &lt;a href=&quot;#group-wikis&quot;&gt;Group Wikis&lt;&#x2F;a&gt;, with the most upvotes ever! Now you can have a central point of collaboration for your team at the group level. Accompanying this, you’ll find &lt;a href=&quot;#deep-level-wiki-navigation&quot;&gt;deep-level wiki navigation&lt;&#x2F;a&gt; in the side bar for easier navigation.&lt;&#x2F;p&gt;

&lt;p&gt;Thanks to another community contribution, you can now easily launch your &lt;a href=&quot;#launch-gitpod-workspaces-directly-from-gitlab&quot;&gt;Gitpod Workspace&lt;&#x2F;a&gt; directly from the GitLab interface.&lt;&#x2F;p&gt;

&lt;p&gt;A picture is worth a thousand words! During an incident, it can be hard to understand the sequence of events from threaded discussions. With the new &lt;a href=&quot;#timeline-view-for-discussions-on-incidents&quot;&gt;Timeline view for discussions in incidents&lt;&#x2F;a&gt;, you can toggle a timeline view of the discussion.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;snippets-and-templates-aid-sharing&quot;&gt;Snippets and templates aid sharing&lt;&#x2F;h2&gt;

&lt;p&gt;Snippets facilitate code sharing among group members. &lt;a href=&quot;#snippets-with-multiple-files&quot;&gt;Snippets with multiple files&lt;&#x2F;a&gt; is now supported inside a single Snippet, so you can create and share complex Snippets composed of multiple parts. The sky’s the limit!&lt;&#x2F;p&gt;

&lt;p&gt;Templates promote best practices and consistency across teams. This month you&#x27;ll find more templates such as a &lt;a href=&quot;#template-for-deploying-to-aws-ec2&quot;&gt;template for deploying to AWS EC2&lt;&#x2F;a&gt;, a new GitLab CI&#x2F;CD &lt;a href=&quot;#get-started-quickly-with-gitlab-and-terraform&quot;&gt;template for Terraform&lt;&#x2F;a&gt;, and the new &lt;a href=&quot;#sast-configuration-ui-improvements&quot;&gt;SAST configuration UI&lt;&#x2F;a&gt; that enables the GitLab CI&#x2F;CD SAST template for users without CI&#x2F;CD experience.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;collaborating-across-tools&quot;&gt;Collaborating across tools&lt;&#x2F;h2&gt;

&lt;p&gt;At GitLab, we want to &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;product&#x2F;categories&#x2F;gitlab-the-product&#x2F;#plays-well-with-others&quot;&gt;play well with others&lt;&#x2F;a&gt;. Whether it’s pulling in &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;development&#x2F;integrations&#x2F;secure.html&quot;&gt;third-party security scanner results&lt;&#x2F;a&gt;, or integrating with other DevOps tools, we want to meet you where you need us. Now with &lt;a href=&quot;#generic-package-registry&quot;&gt;Generic Package Registry&lt;&#x2F;a&gt;, you can store other binary types in GitLab that are not yet supported via raw package feeds and &lt;a href=&quot;#attach-binary-assets-to-releases&quot;&gt;attach binary assets to releases&lt;&#x2F;a&gt;, enabling release and build teams to effectively work in GitLab no matter what type of binary they are building in CI&#x2F;CD.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;of-course-theres-more&quot;&gt;Of course there&#x27;s more!&lt;&#x2F;h3&gt;

&lt;p&gt;These are just a few highlights from the many new features and performance improvements described below.&lt;&#x2F;p&gt;

&lt;p&gt;If you&#x27;d like to preview what&#x27;s coming in next month’s release, be sure to check out the &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;results?search_query=13.6+release+kick+off&quot;&gt;13.6 release kick off video series&lt;&#x2F;a&gt; where the Product Managers highlight key features coming soon. Our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;Upcoming Releases&lt;&#x2F;a&gt; page is where you can find all of the juicy details of our roadmap. Here, you can comment and upvote existing issues and contribute new ideas!&lt;&#x2F;p&gt;

&lt;!--
Reminder: the final paragraph should include the total number of new features
being released, including bugs, performance improvements, and contributions from
non-DevOps stages like Enablement. All of these should be listed in the release
post, either as headers or bullet points.
--&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_5&#x2F;13_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.4 released with Vault for CI variables and Kubernetes Agent</title>
<release>13.4</release>
<link href='https://about.gitlab.com/releases/2020/09/22/gitlab-13-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/09/22/gitlab-13-4-released/</id>
<published>2020-09-22T00:00:00+00:00</published>
<author>
<name>Eric Schurter</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;h2 id=&quot;gitlab-134-released-with-vault-for-ci-variables-kubernetes-agent-and-security-center-and-were-bringing-feature-flags-to-starter&quot;&gt;GitLab 13.4 released with Vault for CI variables, Kubernetes Agent, and Security Center… and we’re bringing feature flags to Starter!&lt;&#x2F;h2&gt;

&lt;p&gt;At GitLab, we are always focusing on how to help your team reduce risk, increase their efficiency, and accelerate their delivery speed with a platform you love. This month, we’re bringing all sorts of goodness that expands visibility into security, lowers vulnerabilities, improves efficiency, makes the user experience better, and helps your team deploy even faster. We hope that you find these top features, and the &lt;strong&gt;53 other new features&lt;&#x2F;strong&gt; packed in this release, useful.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;expanded-security-capabilities&quot;&gt;Expanded security capabilities&lt;&#x2F;h2&gt;

&lt;p&gt;True to form, this month’s release adds several capabilities to your GitLab DevSecOps kit. First, &lt;a href=&quot;#use-hashicorp-vault-secrets-in-ci-jobs&quot;&gt;secrets stored in HashiCorp Vault can now be injected into CI&#x2F;CD jobs&lt;&#x2F;a&gt; as part of the build and deploy process. Next, organizations who want to maintain a separation of code deployment duties can &lt;a href=&quot;#grant-users-deployment-permissions-without-code-access&quot;&gt;promote specific users with Reporter access to the role of Deployer&lt;&#x2F;a&gt;. The Deployer role follows the principle of least privilege access, allowing them to approve merge requests and deploy code to protected environments without requiring access to modify the code itself. Another way you can reduce risk is by using the new &lt;a href=&quot;#introducing-the-gitlab-agent-for-kubernetes&quot;&gt;GitLab Agent for Kubernetes&lt;&#x2F;a&gt;. Operators can deploy to their Kubernetes clusters from GitLab without the need to open their cluster to the entire Internet. We are also introducing automatic versioning support for new Terraform state files with &lt;a href=&quot;#gitlab-managed-terraform-state&quot;&gt;GitLab Managed Terraform state&lt;&#x2F;a&gt; to support compliance and debugging needs. Last but not least, the Instance Security Dashboard has evolved into the &lt;a href=&quot;#security-center&quot;&gt;GitLab Security Center&lt;&#x2F;a&gt; featuring Vulnerability Reporting and Settings.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;better-ux--efficiency&quot;&gt;Better UX &amp;amp; efficiency&lt;&#x2F;h2&gt;

&lt;p&gt;We’ve improved our global search capabilities with &lt;a href=&quot;#quick-navigation-using-the-search-bar&quot;&gt;quick navigation from the search bar&lt;&#x2F;a&gt; to quickly jump to recent issues, groups, projects, settings, and Help topics. We&#x27;re excited about &lt;a href=&quot;#simple-redirect-configuration-file-for-gitlab-pages&quot;&gt;GitLab Pages Redirects&lt;&#x2F;a&gt; for redirecting individual pages and directories within a site, which makes users more efficient at deploying pages sites. And for those who have been wishing for enhanced deployment information, this release enables you to &lt;a href=&quot;#track-environments-at-scale-with-the-environments-dashboard&quot;&gt;manage hundreds of supported project deployments from the Environments dashboard&lt;&#x2F;a&gt;. Tada! 🎉&lt;&#x2F;p&gt;

&lt;h2 id=&quot;open-source-contribution-highlights&quot;&gt;Open source contribution highlights&lt;&#x2F;h2&gt;

&lt;p&gt;We’re introducing &lt;a href=&quot;#inline-code-coverage-remarks-inside-mr-diffs&quot;&gt;inline code coverage remarks inside MR diffs&lt;&#x2F;a&gt;, (contributed by &lt;a href=&quot;#mvp&quot;&gt;this month&#x27;s MVP, Fabio Huser&lt;&#x2F;a&gt;!), providing developers a visual representation of code coverage in the Merge Request diff when doing a review. Knowing whether modified code is covered by a unit test helps speed up code reviews and time to merge and deploy a feature. We have &lt;a href=&quot;#feature-flags-made-available-in-gitlab-starter&quot;&gt;moved feature flags to Starter&lt;&#x2F;a&gt; and plan to move &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;212318&quot;&gt;feature flags to Core in 13.5&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;!--
Suggestion: describe each feature briefly in just a few words, using
anchors to link to their headings (use the relative path). The intro is supposed
to be eyes-catching, so &quot;be happy&quot; about it, describe them enthusiastically.
Focus on what are the advantages on having each of them. For some guidance,
look at the intros of past release posts.
--&gt;

&lt;h3 id=&quot;but-wait-wait-theres-more&quot;&gt;But wait, wait… there’s more!&lt;&#x2F;h3&gt;

&lt;p&gt;As usual, we have way too little space, but still lots and lots of new things we packed into 13.4 to tell you about. Here are a few more of them:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#list-and-revoke-personal-access-tokens-via-api&quot;&gt;List and revoke Personal Access Tokens via API&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#revoke-pats-for-self-managed-credential-inventory&quot;&gt;Revoke PATs for self-managed credential inventory&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#child-pipelines-can-now-trigger-their-own-child-pipelines&quot;&gt;Child pipelines can now trigger their own child pipelines&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#mark-a-to-do-as-done-in-the-design-view&quot;&gt;Mark a to-do as Done in the Design View&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#gitlab-runner-134&quot;&gt;GitLab Runner 13.4 released&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#gitlab-chart-improvements&quot;&gt;GitLab chart improvements&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#smartcard-authentication-support-for-gitlab-helm-chart&quot;&gt;Smartcard authentication support for GitLab Helm chart&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;If you&#x27;d like to preview what&#x27;s coming in next month’s release, be sure to check out our 13.5 &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=Zp7_PNRxMxU&quot;&gt;kickoff video&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;!--
Reminder: the final paragraph should include the total number of new features
being released, including bugs, performance improvements, and contributions from
non-DevOps stages like Enablement. All of these should be listed in the release
post, either as headers or bullet points.
--&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_4&#x2F;13-4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.3 released with coverage-guided fuzz testing and a build matrix for CI&#x2F;CD</title>
<release>13.3</release>
<link href='https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/</id>
<published>2020-08-22T00:00:00+00:00</published>
<author>
<name>Kevin Chu</name>
</author>
<content type='html'>&lt;p&gt;DevSecOps helps teams detect and resolve faults and vulnerabilities early in the software development process. In GitLab 13.3, building secure software is easier with fuzz testing in your development workflow. With &lt;strong&gt;coverage-guided fuzz testing&lt;&#x2F;strong&gt; and &lt;strong&gt;on-demand DAST (Dynamic Application Security Testing)&lt;&#x2F;strong&gt;, discovering real-world software vulnerabilities is faster and more efficient. At the same time, releasing code more frequently is made simpler with the new &lt;strong&gt;build matrix for CI&#x2F;CD&lt;&#x2F;strong&gt;. Finally, the &lt;strong&gt;Pod health dashboard&lt;&#x2F;strong&gt; increases Ops&#x27; efficiency by reducing their context switching: all Kubernetes pods health primitives are in the dashboard. We hope that you find these top features, and the &lt;strong&gt;69 new features&lt;&#x2F;strong&gt; packed in this release, useful.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;faster-remediation-find-and-prevent-defects-and-vulnerabilities-earlier&quot;&gt;Faster remediation: Find and prevent defects and vulnerabilities earlier&lt;&#x2F;h2&gt;

&lt;p&gt;With &lt;a href=&quot;#coverage-guided-fuzz-testing-for-go-and-cc-applications&quot;&gt;coverage-guided fuzz testing&lt;&#x2F;a&gt;, it&#x27;s now easier to efficiently surface and solve vulnerabilities in C, C++, and Go. In GitLab 13.3 all our SAST (Static Application Security Testing) analyzers are &lt;a href=&quot;#sast-security-analyzers-available-for-all&quot;&gt;available to everyone&lt;&#x2F;a&gt; and it has never been easier &lt;a href=&quot;#guided-sast-configuration-experience&quot;&gt;to set them up&lt;&#x2F;a&gt;. Finally, &lt;a href=&quot;#on-demand-dast-scans&quot;&gt;running DAST from the GUI&lt;&#x2F;a&gt; is now more convenient. More importantly, security staff can tackle vulnerabilities faster by leveraging the new &lt;a href=&quot;#dast-vulnerability-evidence&quot;&gt;vulnerability evidence&lt;&#x2F;a&gt; included in the DAST output.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;reduce-cycle-time-release-more-frequently&quot;&gt;Reduce cycle time, release more frequently&lt;&#x2F;h2&gt;

&lt;p&gt;Building powerful workflows is now easy with the new &lt;a href=&quot;#create-a-matrix-of-jobs-using-a-simple-syntax&quot;&gt;build matrix&lt;&#x2F;a&gt;: define keys and values once, release and deploy multiple times. Teams can increase velocity by measuring Merge Request throughput now available in the &lt;a href=&quot;#merge-request-analytics&quot;&gt;MR Analytics Dashboard&lt;&#x2F;a&gt;. Also, MR authors can now integrate code faster by acknowledging their code review requests have been answered &lt;a href=&quot;#merge-request-approvals-show-who-participated-in-the-review&quot;&gt;at a glance&lt;&#x2F;a&gt;. This acknowledgment of fulfilled duties by different roles in MRs are now traceable in the &lt;a href=&quot;#compliance-dashboard-shows-more-information&quot;&gt;Compliance Dashboard&lt;&#x2F;a&gt;. Maintainers can also suggest to their contributors a &lt;a href=&quot;#squash-commits-options&quot;&gt;Squash Commit policy&lt;&#x2F;a&gt;. Lastly, rollouts can be more targeted and controlled using the newly named &lt;a href=&quot;#rename-feature-flag-user-strategies&quot;&gt;feature flags strategy called Percentage of Users&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;enable-your-delivery-teams-to-be-more-productive-and-efficient&quot;&gt;Enable your delivery teams to be more productive and efficient&lt;&#x2F;h2&gt;

&lt;p&gt;Software development is mostly about building and distributing packages. To make that easier and with usability in mind, we overhauled the whole &lt;a href=&quot;#improved-presentation-of-package-metadata-and-activity&quot;&gt;Package registry&lt;&#x2F;a&gt; GUI and made it &lt;a href=&quot;#package-registry-now-available-in-core&quot;&gt;available for everyone in Core&lt;&#x2F;a&gt;. Plus, it has never been easier to publish &lt;a href=&quot;#use-ci-job-token-to-publish-nuget-packages&quot;&gt;NuGet packages&lt;&#x2F;a&gt; in an automated way. Once deployed, your teams won&#x27;t need to worry about the health of their systems. All relevant action can be now taken based on information from the &lt;a href=&quot;#kubernetes-pod-health-dashboard&quot;&gt;Pod health dashboard&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;!--
Suggestion: describe each feature briefly in just a few words, using
anchors to link to their headings (use the relative path). The intro is supposed
to be eyes-catching, so &quot;be happy&quot; about it, describe them enthusiastically.
Focus on what are the advantages on having each of them. For some guidance,
look at the intros of past release posts.
--&gt;

&lt;h3 class=&quot;intro-header&quot; id=&quot;it-doesnt-stop-here-there-is-more&quot;&gt;It doesn’t stop here: there is more!&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab is used by companies with thousands of users in teams working synchronously and asynchronously across continents. To do so, we are focused on improving its &lt;a href=&quot;#concurrent-git-repository-backups&quot;&gt;fault tolerance&lt;&#x2F;a&gt; and &lt;a href=&quot;#gitaly-cluster-reference-transactions&quot;&gt;read&#x2F;write operation synchronicity&lt;&#x2F;a&gt; on every release. Overall, we are making &lt;a href=&quot;#geo-is-faster-and-easier-to-maintain&quot;&gt;GitLab lightning fast&lt;&#x2F;a&gt; across the globe.&lt;&#x2F;p&gt;

&lt;p&gt;Here are several other cool features that you should check out:&lt;&#x2F;p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#drag-and-drop-to-reorder-designs&quot;&gt;&lt;strong&gt;Change the sort order of designs&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#junit-report-improvements&quot;&gt;&lt;strong&gt;JUnit reports are now much easier to read and understand&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#display-strategy-information-on-feature-flags-list-view&quot;&gt;&lt;strong&gt;Feature flag strategy will now show in your feature flag view&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#create-and-manage-it-incidents-in-gitlab&quot;&gt;&lt;strong&gt;Manage IT Incidents&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;If you&#x27;d like to preview what&#x27;s coming in the &lt;em&gt;next&lt;&#x2F;em&gt; release, be sure to check out our 13.4 &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=50fqa7qsI_I&quot;&gt;kickoff video&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;!--
Reminder: the final paragraph should include the total number of new features
being released, including bugs, performance improvements, and contributions from
non-DevOps stages like Enablement. All of these should be listed in the release
post, either as headers or bullet points.
--&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_3&#x2F;13-3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.2 released with Planning Iterations and Load Performance Testing</title>
<release>13.2</release>
<link href='https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/</id>
<published>2020-07-22T00:00:00+00:00</published>
<author>
<name>Justin Farris</name>
</author>
<content type='html'>&lt;p&gt;GitLab 13.2 now helps teams &lt;strong&gt;streamline project planning&lt;&#x2F;strong&gt; with milestone iterations, &lt;strong&gt;collaborate better for faster feedback&lt;&#x2F;strong&gt; with diff changes for wiki pages, and &lt;strong&gt;improve overall performance&#x2F;efficiency&lt;&#x2F;strong&gt; with load performance testing.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header-h3&quot; id=&quot;streamline-agile-project-planning-and-management&quot;&gt;Streamline agile project planning and management&lt;&#x2F;h2&gt;

&lt;p&gt;Managing workflows and planning tasks for different teams can add a significant amount of development disruption to your day. In releasing our &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#minimal-viable-change-mvc&quot;&gt;Minimal Viable Change (MVC)&lt;&#x2F;a&gt; of &lt;a href=&quot;#assign-issues-to-iterations&quot;&gt;&lt;strong&gt;iterations&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; to break down work into smaller, more manageable, chunks, we&#x27;re lessening this disruption and making project planning easier – with many enhancements to come. If your team leverages Jira for project management, it&#x27;s now easier for you to &lt;a href=&quot;#view-jira-issue-list-in-gitlab&quot;&gt;&lt;strong&gt;view Jira issues in GitLab&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; because we believe that GitLab should &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;product&#x2F;categories&#x2F;gitlab-the-product&#x2F;#plays-well-with-others&quot;&gt;play well with others&lt;&#x2F;a&gt; and balance integrations with native capabilities. If you&#x27;re using epics to plan and manage large projects, then you can now protect sensitive content with &lt;a href=&quot;#organize-sensitive-work-into-confidential-epics&quot;&gt;&lt;strong&gt;confidential epics&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;. When you need to update several related epics, you can now &lt;a href=&quot;#bulk-edit-the-epic-for-multiple-issues-from-the-issues-list&quot;&gt;&lt;strong&gt;bulk edit epics&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; to reduce your &quot;tab overload&quot; and the number of clicks it takes to update.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;better-collaboration-for-faster-feedback&quot;&gt;Better collaboration for faster feedback&lt;&#x2F;h2&gt;

&lt;p&gt;Clear communication is key to effective collaboration because it enables development teams to get faster feedback on changes before pushing them to production.  The ability to &lt;a href=&quot;#wiki-page-diffs&quot;&gt;&lt;strong&gt;diff changes for wiki pages&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; now makes edit history comparisons between page versions quicker and simpler, similar to viewing files in a repository.  &lt;a href=&quot;#real-time-feedback-for-gitlab-ciyml-in-web-ide&quot;&gt;&lt;strong&gt;Realtime feedback for&lt;&#x2F;strong&gt; &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; &lt;strong&gt;in the Web IDE&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; makes updating your CI pipeline more efficient by enabling realtime linting and autocompletion. Now you don&#x27;t have to remember all of the parameters when configuring your CI pipeline or switch contexts to get the information you need.&lt;&#x2F;p&gt;

&lt;p&gt;Designers are incredibly important members of the team and 13.2 includes great improvements to design management. It&#x27;s now &lt;a href=&quot;#make-it-easier-to-find-designs-on-an-issue&quot;&gt;&lt;strong&gt;easier to find designs in an issue&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; so it takes less time, and the &lt;a href=&quot;#official-gitlab-figma-plugin&quot;&gt;&lt;strong&gt;official GitLab Figma plugin&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; simplifies the process of uploading from Figma to issues on GitLab.com.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;improved-performance-and-efficiency&quot;&gt;Improved performance and efficiency&lt;&#x2F;h2&gt;

&lt;p&gt;13.2 delivers new updates to improve your team&#x27;s efficiency and performance.  You can now take advantage of &lt;a href=&quot;#advanced-global-search-now-available-on-gitlabcom&quot;&gt;&lt;strong&gt;advanced global search on GitLab.com&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;, a capability that improves search relevancy, performance, and allows for group-wide searches across all projects directly in the UI. Application performance is a challenge every development team faces and now &lt;a href=&quot;#load-performance-testing&quot;&gt;&lt;strong&gt;load performance testing&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; in GitLab makes it easy to run custom load tests as part of your CI&#x2F;CD pipelines to better understand how your application will perform under stress.&lt;&#x2F;p&gt;

&lt;p&gt;Nowadays, it seems like everyone is working from home and are &quot;distributed&quot; more than ever. GitLab Geo helps remote teams work more efficiently by using a local GitLab node, and now offers &lt;a href=&quot;#faster-geo-replication-performance-for-projects&quot;&gt;&lt;strong&gt;improved replication performance for projects&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; to ensure local content is fresh. Last but not least, GitLab &lt;a href=&quot;#include-ci-test-results-in-release-evidence&quot;&gt;&lt;strong&gt;includes CI test results within Release Evidence&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; for easy access in the event you need to provide compliance data or a more efficient way to show relevant changes to production during audit.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-much-more&quot;&gt;And much much more!&lt;&#x2F;h3&gt;

&lt;p&gt;There’s never enough space to highlight all the great features in our releases. An important development for package management that&#x27;s worth noting: GitLab now supports the PHP dependency manager, Composer, so you can &lt;a href=&quot;#manage-php-dependencies-with-the-gitlab-composer-repository&quot;&gt;&lt;strong&gt;discover, share, and install PHP dependencies using GitLab&#x27;s Composer Repository with ease&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Here are several other cool features that you should check out:&lt;&#x2F;p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;a href=&quot;#associate-feature-flags-with-related-issues&quot;&gt;&lt;strong&gt;Associate Feature Flags with related issues&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#container-host-monitoring-and-blocking&quot;&gt;&lt;strong&gt;Container Host Monitoring and Blocking&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#gitlab-runner-support-for-linux-on-ibm-z&quot;&gt;&lt;strong&gt;IBM z&#x2F;OS Mainframe support for GitLab Runner&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;#code-quality-merge-request-widget-moved-to-core&quot;&gt;&lt;strong&gt;Code Quality Merge Request widget moved to Core&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;If you&#x27;d like to preview what&#x27;s coming in the &lt;em&gt;next&lt;&#x2F;em&gt; release, be sure to check out our 13.3 &lt;a href=&quot;https:&#x2F;&#x2F;youtu.be&#x2F;wivB1X_N0QQ&quot;&gt;kickoff video&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_2&#x2F;13-2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.1 released with Alert Management and Code Quality Enhancements</title>
<release>13.1</release>
<link href='https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/</id>
<published>2020-06-22T00:00:00+00:00</published>
<author>
<name>Farnoosh Seifoddini</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;p&gt;GitLab 13.1 is now available, bringing you &lt;strong&gt;expanded alert management&lt;&#x2F;strong&gt;, new tools to help you &lt;strong&gt;track and improve code quality&lt;&#x2F;strong&gt;, and more ways to &lt;strong&gt;keep your code secure and compliant&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;automate-and-expand-alert-management&quot;&gt;Automate and expand Alert Management&lt;&#x2F;h2&gt;

&lt;p&gt;Alerts are essential to application maintenance, but understanding and triaging the range of alerts thrown can dramatically reduce productivity and response time. GitLab’s &lt;a href=&quot;#manage-it-alerts-in-gitlab&quot;&gt;Alert Management&lt;&#x2F;a&gt; aggregates and ranks IT alerts from all of your services to simplify assessment and remediation, increasing productivity and helping you research and address critical issues right away. Key features in 13.1 include &lt;a href=&quot;#assign-gitlab-alerts-to-team-members&quot;&gt;alert assignments&lt;&#x2F;a&gt;, &lt;a href=&quot;#collaborate-on-gitlab-alerts-in-slack&quot;&gt;Slack integration&lt;&#x2F;a&gt;, and &lt;a href=&quot;#create-gitlab-to-dos-when-assigning-alerts&quot;&gt;creating GitLab To-Dos when assigning alerts&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;improve-code-quality&quot;&gt;Improve code quality&lt;&#x2F;h2&gt;

&lt;p&gt;Deployment velocity only matters if you’re deploying high quality code. By &lt;a href=&quot;#run-tests-for-modified-files-first&quot;&gt;prioritizing tests on recently modified code&lt;&#x2F;a&gt;, developers can address errors immediately, without running an entire test suite. &lt;a href=&quot;#graph-code-coverage-changes-over-time-for-a-project&quot;&gt;Code coverage tracking over time&lt;&#x2F;a&gt; surfaces quality trends to developers and managers alike, and native &lt;a href=&quot;#code-intelligence&quot;&gt;code intelligence&lt;&#x2F;a&gt; boosts the speed and accuracy of code reviews by integrating reference material directly into GitLab.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;enhance-and-extend-security-and-compliance&quot;&gt;Enhance and extend security and compliance&lt;&#x2F;h2&gt;

&lt;p&gt;Security matters to everyone, and we&#x27;re committed to lowering the barriers to a fully secure, compliant SDLC. That&#x27;s why we&#x27;re happy to announce that we&#x27;ve migrated &lt;a href=&quot;#rails-sast-analyzer-available-for-all&quot;&gt;Brakeman SAST scanning to Core&lt;&#x2F;a&gt;, allowing every Rails developer—at every product tier—to scan their source code for known vulnerabilities. For compliance-focused organizations, we&#x27;ve released a &lt;a href=&quot;#policy-management-for-container-network-policies&quot;&gt;policy management UI&lt;&#x2F;a&gt; for network container policies,  and we&#x27;ve enabled &lt;a href=&quot;#export-vulnerabilities-list-from-group-security-dashboards&quot;&gt;group-level vulnerability exports&lt;&#x2F;a&gt; to a CSV file for audits or further internal review. In addition, we&#x27;ve made helpful UX improvements to the Security Dashboard, adding &lt;a href=&quot;#filters-persist-on-security-dashboards&quot;&gt;persistent filters&lt;&#x2F;a&gt; and &lt;a href=&quot;#dynamic-issue-status-icons-on-security-dashboards&quot;&gt;issue status icons&lt;&#x2F;a&gt; to help maintain context as you work within the tool.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;These are just a few of the highlights in 13.1. For this release, we also achieved a new milestone in terms of community contribution. For the first time,
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;insights&#x2F;#&#x2F;communityContributions&quot;&gt;more than 300 MRs from the wider community&lt;&#x2F;a&gt; were merged during the release period, and we
appreciate everyone&#x27;s contributions! Read on to learn more about other fantastic productivity improvements, such as &lt;a href=&quot;#accessibility-testing-merge-request-widget&quot;&gt;Accessibility Testing MR Widgets&lt;&#x2F;a&gt;,
&lt;a href=&quot;#mark-any-design-thread-as-resolved&quot;&gt;Design Thread Resolutions&lt;&#x2F;a&gt;, &lt;a href=&quot;#pipeline-success-after-failure-notification&quot;&gt;Pipeline Success Notifications&lt;&#x2F;a&gt;, and more!&lt;&#x2F;p&gt;

&lt;p&gt;If you&#x27;d like to preview what&#x27;s coming in the &lt;em&gt;next&lt;&#x2F;em&gt; release, be sure to check out our &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=AYR3sl8c-co&quot;&gt;13.2 kickoff video&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_1&#x2F;13-1-cover-image-alt.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 13.0 released with Gitaly Clusters, Epic Hierarchy on Roadmaps, and Auto Deploy to ECS</title>
<release>13.0</release>
<link href='https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/</id>
<published>2020-05-22T00:00:00+00:00</published>
<author>
<name>Farnoosh Seifoddini</name>
</author>
<content type='html'>&lt;!--
This is the release blog post file. Add here the introduction only.
All remaining content goes into data&#x2F;release-posts&#x2F;.

**Use the merge request template &quot;Release-Post&quot;, and please set the calendar due
date for each stage (general contributions, review).**

Read through the Release Posts Handbook for more information:
https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;marketing&#x2F;blog&#x2F;release-posts&#x2F;#introduction
--&gt;

&lt;h2 id=&quot;progress-since-gitlab-120&quot;&gt;Progress since GitLab 12.0&lt;&#x2F;h2&gt;

&lt;p&gt;At this milestone release of 13.0, we’d like to take a moment to reflect. We’ve accomplished so much since our 12.0 release! We&#x27;ve put together a &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;version-12-year-in-review&#x2F;&quot;&gt;blog to recap GitLab 12.0 to 12.10&lt;&#x2F;a&gt;. Three favorites from version 12 releases include: &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2020&#x2F;04&#x2F;22&#x2F;gitlab-12-10-released&#x2F;#create-and-view-requirements-in-gitlab&quot;&gt;Requirements Management&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;software_supply_chain_security&#x2F;&quot;&gt;Container Network Security&lt;&#x2F;a&gt;, and &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;releases&#x2F;2020&#x2F;01&#x2F;22&#x2F;gitlab-12-7-released&#x2F;#parent-child-pipelines&quot;&gt;Parent-child pipelines&lt;&#x2F;a&gt;. In addition to product enhancements, we&#x27;ve embraced &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;press&#x2F;releases&#x2F;2020-04-21-gitlab-ramps-up-channel-and-partner-investment-with-launch-of-a-new-global-partner-program&#x2F;&quot;&gt;partnerships&#x2F;integrations&lt;&#x2F;a&gt;, adding &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;development&#x2F;integrations&#x2F;secure.html&quot;&gt;integration guidelines&lt;&#x2F;a&gt; for third-party security scanners, and have grown our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;services&#x2F;catalog&#x2F;&quot;&gt;professional services&lt;&#x2F;a&gt; to help you with things like Jira and Jenkins migrations. Our new channel, &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;playlist?list=PLFGfElNsQthYDx0A_FaNNfUm9NHsK6zED&quot;&gt;Learn@GitLab&lt;&#x2F;a&gt; makes it easy to find many new how-to videos such as &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=e0iQD1qgxZg&amp;amp;list=PLFGfElNsQthYDx0A_FaNNfUm9NHsK6zED&amp;amp;index=10&amp;amp;t=0s&quot;&gt;Getting started with CI&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;iteration-is-the-key-to-resilience&quot;&gt;Iteration is the key to resilience&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab is enabling IT and business teams to adapt, respond, and thrive. &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;power-of-iteration&#x2F;&quot;&gt;Iteration&lt;&#x2F;a&gt; is the key. To do so you must collaborate rapidly, optimize for efficiency, and automate processes to handle security and compliance while you focus on delivering business value. GitLab 13.0 can help you iterate quickly and with greater insight. At the same time, access to Git repositories is critical, and we have enhanced our &lt;a href=&quot;#gitaly-cluster-for-high-availability-git-storage&quot;&gt;Gitaly cluster for high availability Git storage&lt;&#x2F;a&gt; to ensure there are always multiple warm replicas ready to take over if an outage occurs.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;rapidly-collaborate-and-respond-across-the-entire-team&quot;&gt;Rapidly collaborate and respond across the entire team&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab builds upon capabilities that help with &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=OFNUjvgm2_4&quot;&gt;collaborative development&lt;&#x2F;a&gt;, reporting, organizing, and managing work. Version control is foundational to collaboration and, with 13.0, we have added &lt;a href=&quot;#versioned-snippets&quot;&gt;version control for snippets&lt;&#x2F;a&gt;. To manage more complex projects, 13.0 allows you to &lt;a href=&quot;#view-epic-hierarchy-on-a-roadmap&quot;&gt;view the epic hierarchy on your roadmap&lt;&#x2F;a&gt;, &lt;a href=&quot;#view-milestones-on-the-roadmap&quot;&gt;view how your epics line up with your various milestones&lt;&#x2F;a&gt;, and &lt;a href=&quot;#update-releases-milestone-in-web-ui&quot;&gt;add a single or multiple milestones to your releases&lt;&#x2F;a&gt; while &lt;a href=&quot;#raise-warning-when-closing-an-issue-with-open-blockers&quot;&gt;alerts upon closing an issue with open blockers&lt;&#x2F;a&gt; help you focus on critical path items.&lt;&#x2F;p&gt;

&lt;p&gt;Designers are an important part of the development team. While working on one of the most popular new features, the &lt;a href=&quot;#dark-theme-in-the-web-ide&quot;&gt;dark themed web IDE&lt;&#x2F;a&gt;, we &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;creating-a-dark-ui-for-gitlabs-web-ide&#x2F;&quot;&gt;learned how&lt;&#x2F;a&gt; to pull designers in to collaborate more closely. At the same time, we moved &lt;a href=&quot;#design-management-moved-to-core&quot;&gt;Design Management to core&lt;&#x2F;a&gt; recognizing users who are designing products as individual contributors.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;optimize-for-efficiency&quot;&gt;Optimize for efficiency&lt;&#x2F;h3&gt;

&lt;p&gt;As many businesses strive to be more responsive and efficient, GitLab helps streamline existing software development processes. New features aimed at efficiency include things like &lt;a href=&quot;#auto-deploy-to-ecs&quot;&gt;simplified deployment to Amazon ECS&lt;&#x2F;a&gt; and a new consolidated &lt;a href=&quot;#aggregate-it-alerts-from-external-tools-in-gitlab&quot;&gt;list of alerts&lt;&#x2F;a&gt; that provides a single interface aggregating IT alerts originating from multiple sources. In addition, Terraform users will rejoice. GitLab 13.0 lets you &lt;a href=&quot;#review-summary-of-terraform-plan-in-merge-requests&quot;&gt;review the summary of &lt;code&gt;terraform plan&lt;&#x2F;code&gt; in Merge Requests&lt;&#x2F;a&gt; and &lt;a href=&quot;#gitlab-http-terraform-state-backend&quot;&gt;use GitLab as an HTTP Terraform state backend&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;trust-your-processes-and-dont-sacrifice-security-or-compliance&quot;&gt;Trust your processes and don’t sacrifice security or compliance&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab helps businesses embrace security and compliance controls end-to-end in the software development lifecycle, reducing risk and freeing up resources to focus on business critical needs. Our Application Security Testing capabilities help you &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=UgCHtr-6uG8&amp;amp;list=PLFGfElNsQthYDx0A_FaNNfUm9NHsK6zED&amp;amp;index=2&amp;amp;t=0s&quot;&gt;find and fix security vulnerabilities earlier&lt;&#x2F;a&gt; and for these, GitLab was just named as a &lt;a href=&quot;https:&#x2F;&#x2F;page.gitlab.com&#x2F;resources-report-gartner-magic-quadrant-ast.html&quot;&gt;Niche Player&lt;&#x2F;a&gt; in the 2020 Gartner Magic Quadrant for Application Security Testing. Since Gartner&#x27;s evaluation of 12.4, we have added many new features. In 13.0 alone we&#x27;ve added the ability to &lt;a href=&quot;#rest-api-support-for-dast-scans&quot;&gt;scan REST APIs via DAST&lt;&#x2F;a&gt; and a &lt;a href=&quot;#secret-detection-for-the-full-history-of-a-repository&quot;&gt;full commit history scan for secrets&lt;&#x2F;a&gt; for even greater detection. More importantly, we have rearchitected the way we handle &lt;a href=&quot;#standalone-vulnerability-objects&quot;&gt;vulnerability objects&lt;&#x2F;a&gt;. This enabled the ability to &lt;a href=&quot;#export-vulnerabilities-list-from-project-security-dashboard&quot;&gt;export vulnerabilities from the security dashboard&lt;&#x2F;a&gt; and will unlock many more robust &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;security_risk_management&#x2F;security-insights&#x2F;vulnerability_management&#x2F;&quot;&gt;Vulnerability Management&lt;&#x2F;a&gt; capabilities in the future.&lt;&#x2F;p&gt;

&lt;p&gt;In addition to security scanning, GitLab automates policies and, with 13.0, provides more granular control with new features such as setting a &lt;a href=&quot;#implement-a-deployment-freeze-with-the-freeze-period-api&quot;&gt;deployment freeze with the Freeze Period API&lt;&#x2F;a&gt; to easily prevent an unintended production release during a specified period of time. To simplify audits, you can now &lt;a href=&quot;#filtered-search-for-instance-level-audit-events&quot;&gt;filter search for instance-level audit events&lt;&#x2F;a&gt; as part of a the &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;epics&#x2F;3179&quot;&gt;larger epic&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;looking-ahead&quot;&gt;Looking ahead&lt;&#x2F;h2&gt;

&lt;p&gt;We are excited about our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;upcoming releases&lt;&#x2F;a&gt;, particularly features that will help you:&lt;&#x2F;p&gt;
&lt;ul&gt;
  &lt;li&gt;Establish a &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;dev&#x2F;#enterprise-compliance&quot;&gt;compliance framework&lt;&#x2F;a&gt; and automatically adopt associated controls and reporting&lt;&#x2F;li&gt;
  &lt;li&gt;Iterate with better insight with &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;epics&#x2F;2966&quot;&gt;A&#x2F;B testing&lt;&#x2F;a&gt; and control via several Feature Flag enhancements (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;35558&quot;&gt;filter feature flags by status&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;34813&quot;&gt;A&#x2F;B testing based on feature flags&lt;&#x2F;a&gt;, and the &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;33394&quot;&gt;ability to create feature flag from merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
  &lt;li&gt;Identify bottlenecks and waste by visually depicting &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;210315&quot;&gt;Value Stream Analytics stages as a flow&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;214729&quot;&gt;Manage policies&lt;&#x2F;a&gt; and let GitLab automate their use, including things like an &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;216074&quot;&gt;out-of-the-box Container Network Policy set&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
  &lt;li&gt;Work within an ecosystem to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;33906&quot;&gt;fuzz test&lt;&#x2F;a&gt; application APIs, and &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab&#x2F;-&#x2F;issues&#x2F;28321&quot;&gt;read Vault CI variables&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Want to see the complete list of what’s coming out NEXT month? Our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;upcoming-releases&#x2F;&quot;&gt;roadmap&lt;&#x2F;a&gt; is transparent and always available for you to contribute!&lt;&#x2F;p&gt;

&lt;p&gt;Now, without further ado, check out more fabulous updates in 13.0 below!&lt;&#x2F;p&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;13_0&#x2F;13-0-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.10 released with Requirements Management and   Autoscaling CI on AWS Fargate</title>
<release>12.10</release>
<link href='https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-released/</id>
<published>2020-04-22T00:00:00+00:00</published>
<author>
<name>Farnoosh Seifoddini</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.10 now helps teams &lt;strong&gt;streamline and improve compliance&lt;&#x2F;strong&gt; with requirements management, &lt;strong&gt;reduce cycle time and accelerate software delivery&lt;&#x2F;strong&gt; with CI with auto-scaling on AWS Fargate, and &lt;strong&gt;more efficiently manage a portfolio&lt;&#x2F;strong&gt; of projects with issue and epic health status.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header-h3&quot; id=&quot;compliance-is-easier&quot;&gt;Compliance is easier&lt;&#x2F;h2&gt;

&lt;p&gt;Compliance is a common challenge in most large organizations, where teams and projects need to demonstrate they followed the organization’s processes and procedures, and delivered what was actually &quot;required&quot;. &lt;em&gt;Did the project actually address the business requirements&lt;&#x2F;em&gt; is a common question, and with 12.10, we’re starting to deliver &lt;a href=&quot;#create-and-view-requirements-in-gitlab&quot;&gt;&lt;strong&gt;requirements management&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; as a distinct category in GitLab to help teams define, track, and manage business requirements. Also, demonstrating project and release compliance just got a little easier in GitLab 12.10, as there&#x27;s no longer a need to use scripts to compare &lt;a href=&quot;#compare-release-evidence-over-time&quot;&gt;&lt;strong&gt;release evidence over time&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;, helping teams document and prove that the project is in &quot;compliance&quot;.
The new project &lt;a href=&quot;#compliance-framework-labels-for-projects&quot;&gt;&lt;strong&gt;compliance framework label&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; makes it easy for organizations to indicate that a specific project is required to comply with specific compliance frameworks.
Speaking of compliance frameworks, to help projects that are subject to HIPAA audits and compliance, the new &lt;a href=&quot;#new-hipaa-audit-protocol-project-template&quot;&gt;&lt;strong&gt;HIPAA audit protocol project template&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; gives them a head start.
It&#x27;s also easier to protect your secrets with improved &lt;a href=&quot;#retrieve-cicd-secrets-from-hashicorp-vault&quot;&gt;&lt;strong&gt;HashiCorp Vault Integration&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;, which helps keep your projects compliant with your security policies.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;reduce-cycle-time-and-accelerate-delivery-on-aws&quot;&gt;Reduce Cycle Time and Accelerate Delivery on AWS&lt;&#x2F;h2&gt;

&lt;p&gt;The last thing you need is another bottleneck that potentially slows down delivery and that’s why we’ve supported autoscaling GitLab CI runners for a very, very long time. In GitLab 12.10, we’re extending our autoscaling ability on AWS Fargate to &lt;a href=&quot;#autoscaling-gitlab-ci-jobs-on-aws-fargate&quot;&gt;&lt;strong&gt;auto-scale runners&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; so pipelines can efficiently scale to meet demand. Speaking of AWS, it&#x27;s now faster and easier to configure your application to deploy to AWS with &lt;a href=&quot;#easy-to-configure-aws-deployment-variables&quot;&gt;&lt;strong&gt;predefined AWS deployment variables&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;, where GitLab has added AWS deployment variables and also helps with format validation.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;efficiently-manage-projects&quot;&gt;Efficiently manage projects&lt;&#x2F;h2&gt;

&lt;p&gt;Managing multiple projects and associated issues can be hard to juggle. With all the information there is to track, it&#x27;s hard to know where there might be problems. Now in GitLab 12.10, it’s easy for teams to track and share the &lt;a href=&quot;#epic-and-issue-health-tracking&quot;&gt;&lt;strong&gt;health status&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; of issues so that it’s simple to visualize the overall health of the epic. Additionally, we’re making it easier to &lt;a href=&quot;#import-issues-from-jira-to-gitlab&quot;&gt;&lt;strong&gt;import issues from Jira&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; into GitLab so that teams can spend less time switching between tools and more time focused on building great software.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-much-more&quot;&gt;And much much more!&lt;&#x2F;h3&gt;

&lt;p&gt;There’s never enough space to highlight all the great features in our releases. Here’s a few other cool features that you should check out: &lt;a href=&quot;#build-publish-and-share-python-packages-to-the-gitlab-pypi-repository&quot;&gt;Python PyPI repository&lt;&#x2F;a&gt; and &lt;a href=&quot;#view-issue-and-mr-feed-by-newest-activity-first&quot;&gt;View Issue and MR activity- newest first&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;!--
Reminder: the final paragraph should include the total number of new features
being released, including bugs, performance improvements, and contributions from
non-DevOps stages like Enablement. All of these should be listed in the release
post, either as headers or bullet points.


These are just a few highlights from the `A` new and improved features, and `B`
performance improvements described below, and a small selection from the `C`
merge requests made in X.Y. Check out more great updates below, such as...
--&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_10&#x2F;cover-image-12-10.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.9 released with Vault App, Code Quality Reports and Group Deploy Tokens</title>
<release>12.9</release>
<link href='https://about.gitlab.com/releases/2020/03/22/gitlab-12-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/03/22/gitlab-12-9-released/</id>
<published>2020-03-22T00:00:00+00:00</published>
<author>
<name>Larissa Lane</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.9 is now available to help DevOps leaders achieve &lt;strong&gt;enhanced security&lt;&#x2F;strong&gt; with management of your secrets via HashiCorp Vault managed application, &lt;strong&gt;better visibility&lt;&#x2F;strong&gt; with code quality reports &amp;amp; customizable value stream analytics, and &lt;strong&gt;easier administration&lt;&#x2F;strong&gt; with group deploy tokens and API administration of deploy tokens.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;secure-your-applications-with-secrets-management-and-vulnerability-remediation&quot;&gt;Secure your applications with Secrets Management and Vulnerability Remediation&lt;&#x2F;h2&gt;

&lt;p&gt;Many organizations are centralizing the storage of secrets for infrastructure and applications in external secrets management solutions, including HashiCorp Vault. With GitLab 12.9, we enable users to leverage &lt;a href=&quot;https:&#x2F;&#x2F;www.vaultproject.io&#x2F;&quot;&gt;HashiCorp Vault&lt;&#x2F;a&gt; to securely manage keys, tokens, and other secrets at the project level by installing it as a &lt;a href=&quot;#hashicorp-vault-gitlab-cicd-managed-application&quot;&gt;managed application&lt;&#x2F;a&gt; within a Kubernetes Cluster. For current HashiCorp Vault users, you can follow our Bring Your Own Vault Integration progress in &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;-&#x2F;epics&#x2F;2868&quot;&gt;gitlab&amp;amp;2868&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;When Container Scanning detects vulnerabilities, GitLab 12.9 can now give &lt;a href=&quot;#suggested-solution-for-container-scanning&quot;&gt;a suggested solution for the vulnerability&lt;&#x2F;a&gt;, when available. You can choose to remediate the vulnerability with a merge request, which will automatically update the packages in the container base image, helping you resolve container security issues swiftly and efficiently.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;better-visibility-with-customizable-value-stream-analytics-and-code-quality-reports&quot;&gt;Better visibility with Customizable Value Stream Analytics and Code Quality Reports&lt;&#x2F;h2&gt;

&lt;p&gt;&lt;a href=&quot;&#x2F;solutions&#x2F;value-stream-management&#x2F;&quot;&gt;Value Stream Analytics&lt;&#x2F;a&gt; helps organizations visualize their end-to-end workstream and identify inefficiencies, in order to continuously improve how they deliver value. Previously the lifecycle stages were fixed to the &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;stages-devops-lifecycle&#x2F;&quot;&gt;DevOps loop&lt;&#x2F;a&gt;, which may not be suitable for everyone, as some teams may follow a different workflow. With GitLab 12.9, you have more control to &lt;a href=&quot;#customizable-value-stream-analytics&quot;&gt;customize the stages&lt;&#x2F;a&gt; to reflect the right metrics for your business. Each new stage can have specific trigger events that define the entry or exit of the stage, allowing you to focus on improvements based on your defined key performance indicators. Be on the lookout for &lt;a href=&quot;&#x2F;direction&#x2F;plan&#x2F;value_stream_management&#x2F;&quot;&gt;more capabilities&lt;&#x2F;a&gt; in our upcoming releases.&lt;&#x2F;p&gt;

&lt;p&gt;Previously, developers used the Code Quality feature in the merge request to understand the impact on quality of the target branch. However, this does not give insight to developers and managers into other code quality issues across the project. With GitLab 12.9, we have introduced a &lt;a href=&quot;#full-code-quality-report&quot;&gt;Full Code Quality Report&lt;&#x2F;a&gt; that summarizes the quality issues across the project.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;improve-efficiencies-with-group-deploy-tokens&quot;&gt;Improve efficiencies with Group Deploy Tokens&lt;&#x2F;h2&gt;

&lt;p&gt;For any organization working with containers, it is critical for their orchestrator to have secure and ongoing access to their container registry. Previously, we introduced &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;deploy_tokens&#x2F;&quot;&gt;Project Deploy Tokens&lt;&#x2F;a&gt; to provide long lived read-only authentication to the registry without being associated with a particular user or having unnecessary access rights.&lt;&#x2F;p&gt;

&lt;p&gt;With GitLab 12.9, managing deploy tokens in bulk is now more efficient, as we are not only introducing &lt;a href=&quot;#group-deploy-tokens&quot;&gt;deploy tokens at the group level&lt;&#x2F;a&gt; but also APIs to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;deploy_tokens.html&quot;&gt;create, list and revoke deploy tokens&lt;&#x2F;a&gt;. If a specific project requires to use different tokens, project-level deploy tokens override group level deploy tokens.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;There are so many great features in GitLab 12.9, that we couldn&#x27;t possibly highlight them all. A few favorites include &lt;a href=&quot;#web-application-firewall-waf-statistics-reporting&quot;&gt;WAF Statistics Report&lt;&#x2F;a&gt;, &lt;a href=&quot;#group-level-roadmap-now-available-in-premium&quot;&gt;Group level Roadmaps now available in Premium&lt;&#x2F;a&gt;, and &lt;a href=&quot;#log-aggregation-in-core&quot;&gt;Log Aggregation now available in Core&lt;&#x2F;a&gt;! Keep reading below to get details on every feature release.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_9&#x2F;12_9-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.8 released with Log Explorer, NuGet, and Compliance</title>
<release>12.8</release>
<link href='https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/</id>
<published>2020-02-22T00:00:00+00:00</published>
<author>
<name>Tim Rizzi</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.8 is here celebrating &quot;one place!&quot; Get one place for your logs, one place for your NuGet packages, and one place for your compliance activity just like GitLab is one place for your entire DevOps lifecycle.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;triage-faster-with-the-new-log-explorer&quot;&gt;Triage faster with the new Log Explorer&lt;&#x2F;h2&gt;

&lt;p&gt;When triaging an incident or validating the status of your service you need to be able to explore Kubernetes Pod Logs from across your entire application. Previously, this was a painful process as you could only see limited logs, couldn&#x27;t go back in time, and didn&#x27;t have search. This was complex and time-consuming enough that it could make using Pod Logs impractical for meaningful analysis and instead limit it to simple troubleshooting use cases.&lt;&#x2F;p&gt;

&lt;p&gt;Now, a new &lt;a href=&quot;#explore-aggregated-logs&quot;&gt;Log Explorer&lt;&#x2F;a&gt; lets you interact with all your logs aggregated into one place. Powerful features including filtering, time picker, and full-text search let you quickly get the information you need. This important milestone moves our &lt;a href=&quot;&#x2F;direction&#x2F;monitor&#x2F;platform-insights&#x2F;&quot;&gt;Logging category&lt;&#x2F;a&gt; from &lt;code&gt;minimal&lt;&#x2F;code&gt; to &lt;code&gt;viable&lt;&#x2F;code&gt;!  To get started, &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;clusters&#x2F;applications.html#elastic-stack&quot;&gt;install the Elastic stack&lt;&#x2F;a&gt; on your Kubernetes cluster with just one click using the GitLab Managed app, and your logs will be automatically collected and aggregated.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;efficiently-store-and-share-c-and-net-resources&quot;&gt;Efficiently store and share C# and .NET resources&lt;&#x2F;h2&gt;

&lt;p&gt;Windows has a large, active, and growing development community. While GitLab has already had built-in package management for &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;packages&#x2F;conan_repository&#x2F;index.html&quot;&gt;C&#x2F;C++&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;packages&#x2F;maven_repository&#x2F;index.html&quot;&gt;Java&lt;&#x2F;a&gt;, and &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;packages&#x2F;npm_registry&#x2F;index.html&quot;&gt;Node.js&lt;&#x2F;a&gt;, teams writing applications in C# and .NET still needed to use tools external to GitLab in order to store and manage their binaries. This meant they were missing out on the &lt;a href=&quot;&#x2F;topics&#x2F;single-application&#x2F;&quot;&gt;benefits of using a single application&lt;&#x2F;a&gt; across their DevOps lifecycle.&lt;&#x2F;p&gt;

&lt;p&gt;Now, GitLab 12.8 gives teams writing code in C# and .NET a built-in &lt;a href=&quot;#build-publish-and-share-packages-to-the-gitlab-nuget-net-repository&quot;&gt;NuGet repository&lt;&#x2F;a&gt; so they have one place to manage and share project binaries both privately and publicly. Developers can now benefit from having their source code, CI&#x2F;CD pipelines, and the resulting packages all in the same application so they can get work done faster with less effort.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;manage-risk-with-the-compliance-dashboard&quot;&gt;Manage risk with the Compliance Dashboard&lt;&#x2F;h2&gt;

&lt;p&gt;Merge requests (MRs) are an elegant and powerful change management tool for keeping a record of changes and approvals. Release teams use MRs to track deployments, and infrastructure teams use MRs to practice &lt;a href=&quot;&#x2F;topics&#x2F;gitops&#x2F;gitops-multicloud-deployments-gitlab&#x2F;&quot;&gt;GitOps&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Additionally, tracking all MR activity can be critical for organizations that have specific company policies that govern their operations in order to adhere to compliance frameworks, such as SOC 2, ISO 27001, GDPR, SOX, HIPAA, or PCI-DSS, and have specific company policies that govern their operations.&lt;&#x2F;p&gt;

&lt;p&gt;Some examples of governing policies are:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;All MRs have a related issue with detailed information about the change(s)&lt;&#x2F;li&gt;
  &lt;li&gt;All MRs are reviewed and approved by someone who isn&#x27;t the author&lt;&#x2F;li&gt;
  &lt;li&gt;All MRs pass QA and security testing&lt;&#x2F;li&gt;
  &lt;li&gt;Any exceptions to the requirements require separate approval.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Previously, GitLab users lacked the necessary tools to effectively manage their GitLab environment&#x27;s change management and compliance. Project-level activity was confined to each project, and there was no easy way to view this information in aggregate at the group level. This lack of control and insight created increased potential for risk, reducing users&#x27; ability to manage compliance within GitLab.&lt;&#x2F;p&gt;

&lt;p&gt;We have a &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;software_supply_chain_security&#x2F;compliance&quot;&gt;vision for adding robust compliance management&lt;&#x2F;a&gt; to Gitlab. As a first step towards this vision, we&#x27;re starting with a &lt;a href=&quot;#compliance-dashboard&quot;&gt;Compliance Dashboard&lt;&#x2F;a&gt; which provides a view of the most recent merge requests for each project in a Group. With the capabilities available today, you can manage auditing of your code changes for releases and GitOps from one place. Similarly, this makes it easier for compliance-focused organizations to quickly understand which projects might have greater risk and therefore warrant extra attention. Be on the lookout for &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;software_supply_chain_security&#x2F;compliance&#x2F;compliance-management&#x2F;#whats-next--why&quot;&gt;more capabilities and improvements&lt;&#x2F;a&gt; in our coming releases.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;These are just a few highlights in 12.8. Check out the other great updates, such as &lt;a href=&quot;#blocking-issue-support&quot;&gt;blocking issues&lt;&#x2F;a&gt;, &lt;a href=&quot;#leverage-policies-to-remove-docker-images&quot;&gt;Docker image expiration policies&lt;&#x2F;a&gt;, and &lt;a href=&quot;#single-level-epics-now-available-in-premium&quot;&gt;Single-level Epics, now available in Premium&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_8&#x2F;12_8-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.7 released with Parent-Child Pipelines and Windows Shared Runners Beta</title>
<release>12.7</release>
<link href='https://about.gitlab.com/releases/2020/01/22/gitlab-12-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2020/01/22/gitlab-12-7-released/</id>
<published>2020-01-22T00:00:00+00:00</published>
<author>
<name>James Ramsay</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.7 is now available with improvements to make your pipelines and teams more efficient and effective. Automation and pipelines are foundational for effective DevOps teams, and in 12.7 we’re delivering multiple improvements to make you faster and more efficient, including &lt;a href=&quot;#parent-child-pipelines&quot;&gt;Parent-Child Pipelines&lt;&#x2F;a&gt;, &lt;a href=&quot;#pipeline-resource-groups&quot;&gt;Pipeline Resource Groups&lt;&#x2F;a&gt;, and &lt;a href=&quot;#windows-shared-runners-on-gitlabcom-beta&quot;&gt;Windows Shared Runners in beta on GitLab.com&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Because teams manage so much of their work in Merge Requests, &lt;a href=&quot;#code-review-analytics&quot;&gt;Code Review Analytics&lt;&#x2F;a&gt; and &lt;a href=&quot;#display-the-deployment-time-of-a-merge-request&quot;&gt;more informative Merge Request widgets&lt;&#x2F;a&gt; will make it easier to optimize quality and cycle time.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;faster-and-more-efficient-pipelines-and-teams&quot;&gt;&lt;strong&gt;Faster and More Efficient Pipelines and Teams&lt;&#x2F;strong&gt;&lt;&#x2F;h2&gt;

&lt;p&gt;Large, complex pipelines can be both slow to execute and hard to understand. &lt;a href=&quot;#parent-child-pipelines&quot;&gt;Parent-child pipelines&lt;&#x2F;a&gt; will speed things up by allowing separate, child pipelines to run concurrently. By also separating and simplifying visualization and configuration per pipeline, and even allowing shared, reusable configuration, parent-child pipelines are easier to manage and will make both your CI&#x2F;CD and your team more efficient.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;manage-shared-pipeline-resources&quot;&gt;&lt;strong&gt;Manage Shared Pipeline Resources&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;Many organizations have shared environments and resources where they want to prevent multiple changes from being made at the same time. &lt;a href=&quot;#pipeline-resource-groups&quot;&gt;Resource Groups&lt;&#x2F;a&gt; help you limit pipeline concurrency to more efficiently and effectively manage jobs and resources.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;windows-shared-runners-beta&quot;&gt;&lt;strong&gt;Windows Shared Runners Beta&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;Windows developers can now choose to take advantage of &lt;a href=&quot;#windows-shared-runners-on-gitlabcom-beta&quot;&gt;Shared Runners on GitLab.com&lt;&#x2F;a&gt;, instead of or in addition to setting up their own. This beta release enables running CI&#x2F;CD jobs on Windows virtual machines with the added efficiency of a fully-managed, auto-scaling, and secure environment, managed by the GitLab.com team.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;faster-merge-request-management&quot;&gt;&lt;strong&gt;Faster Merge Request Management&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;Timely code review keeps your team shipping. &lt;a href=&quot;#code-review-analytics&quot;&gt;Code Review Analytics&lt;&#x2F;a&gt; will make it easy to find Merge Requests in review that need intervention, helping teams manage their cycle time. &lt;a href=&quot;#display-the-deployment-time-of-a-merge-request&quot;&gt;Improved Merge Request widgets&lt;&#x2F;a&gt; now show when changes have made it to a specific environment, saving time tracking down the latest deploy.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-more&quot;&gt;&lt;strong&gt;And Much More&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;These are just a few highlights from the 45 new and improved features, and 12 performance improvements described below, and a small selection from the 1,593 merge requests made in 12.7. Check out more great updates below, such as &lt;a href=&quot;#automatically-stage-all-changes-in-web-ide&quot;&gt;automatically staging all changes in our Web IDE&lt;&#x2F;a&gt; and &lt;a href=&quot;#share-group-access-with-another-group&quot;&gt;the ability to share group access with another group&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_7&#x2F;12_7-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.6 released with Security Scorecard and Release Evidence</title>
<release>12.6</release>
<link href='https://about.gitlab.com/releases/2019/12/22/gitlab-12-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/12/22/gitlab-12-6-released/</id>
<published>2019-12-22T00:00:00+00:00</published>
<author>
<name>Gabe Weaver</name>
</author>
<content type='html'>&lt;p&gt;A common challenge many development leaders face is having visibility into the overall &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;solutions&#x2F;security-compliance&#x2F;&quot;&gt;application security&lt;&#x2F;a&gt; and &lt;a href=&quot;&#x2F;solutions&#x2F;compliance&#x2F;&quot;&gt;compliance&lt;&#x2F;a&gt; status of their projects. This month&#x27;s GitLab release helps you more efficiently monitor the application security and release compliance of your projects.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;security-visibility-with-project-security-status&quot;&gt;&lt;strong&gt;Security Visibility with Project Security Status&lt;&#x2F;strong&gt;&lt;&#x2F;h2&gt;

&lt;p&gt;With GitLab 12.6, a new &lt;a href=&quot;#quickly-understand-your-at-risk-projects-with-project-security-grades&quot;&gt;Project Security Status panel&lt;&#x2F;a&gt; shows how projects are ranked according to their security profile. This makes it easier for development leaders to quickly understand which projects may have greater risk and therefore might warrant additional attention to address specific issues.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;streamline-audits-with-release-evidence&quot;&gt;&lt;strong&gt;Streamline Audits with Release Evidence&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;Almost every enterprise development team is expected to document and demonstrate that each release complies with their organization’s policies, procedures, and controls. Often it means they have a manual processes to save the documentation so that future audits can review the compliance evidence. GitLab 12.6 makes audits and compliance much easier, with a &lt;a href=&quot;#automated-release-evidence-collection-to-support-audits&quot;&gt;release evidence file&lt;&#x2F;a&gt; in the form of a JSON object that includes links to the milestones and issues that were included in the release, which can help to streamline future audits.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;efficiently-manage-and-share-cc-resources&quot;&gt;&lt;strong&gt;Efficiently Manage and Share C&#x2F;C++ Resources&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;Many teams are actively developing new high performance applications in C and C++ and they need the ability to easily store and manage the compiled files and binaries from their projects.  GitLab 12.6 now helps teams writing code in C and C++ to manage and share both privately and publicly the binaries from their projects with the popular &lt;a href=&quot;#manage-cc-packages-via-conan-within-gitlabs-package-registry&quot;&gt;Conan repository built into GitLab&lt;&#x2F;a&gt;. They can now benefit from having source code, automated GitLab CI pipelines and the resulting packages in the same application which will help improve their overall efficiency and velocity.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-more&quot;&gt;&lt;strong&gt;And Much More&lt;&#x2F;strong&gt;&lt;&#x2F;h3&gt;

&lt;p&gt;These are just a few of the highlights in 12.6. Check out the other great updates, such as &lt;a href=&quot;#dependency-scanning-for-java-gradle-projects&quot;&gt;dependency scanning for Java Gradle projects&lt;&#x2F;a&gt; and &lt;a href=&quot;#maintain-a-consolidated-commit-history-with-squash-and-merge-in-merge-trains&quot;&gt;support for squash-and-merge within Merge Trains&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Also, &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;registration is open&lt;&#x2F;a&gt; for the next &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;GitLab Commit User Conference&lt;&#x2F;a&gt; in San Francisco, January 14.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_6&#x2F;12_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.5 with EKS Cluster Creation &amp; Environments Dashboard</title>
<release>12.5</release>
<link href='https://about.gitlab.com/releases/2019/11/22/gitlab-12-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/11/22/gitlab-12-5-released/</id>
<published>2019-11-22T00:00:00+00:00</published>
<author>
<name>Patrick Deuley</name>
</author>
<content type='html'>&lt;p&gt;To deliver high-quality software as efficiently as possible, enterprises need to support a wide range of infrastructure,
&lt;a href=&quot;https:&#x2F;&#x2F;medium.com&#x2F;gitlab-magazine&#x2F;multi-cloud-maturity-model-2de185c01dd7&quot;&gt;across multiple clouds&lt;&#x2F;a&gt;. This month’s GitLab 12.5 release makes it even easier to
configure, monitor, and manage projects across a variety of configurations.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;create-and-deploy-to-an-eks-cluster-from-gitlab&quot;&gt;Create and deploy to an EKS cluster from GitLab&lt;&#x2F;h2&gt;

&lt;p&gt;Like 85% of enterprises, &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;blog&#x2F;gitlab-ci-cd-is-for-multi-cloud&#x2F;&quot;&gt;GitLab believes in multicloud&lt;&#x2F;a&gt;. It’s critical that you can deploy to the cloud of your choice as seamlessly as possible. With that in mind, we’re thrilled to announce that you can now &lt;a href=&quot;#easily-create-and-deploy-to-an-eks-cluster&quot;&gt;create Kubernetes clusters on Amazon’s EKS&lt;&#x2F;a&gt; with a few clicks. The workflow is similar to how easy it is to create a cluster with &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;partners&#x2F;technology-partners&#x2F;google-cloud-platform&#x2F;&quot;&gt;Google’s GKE&lt;&#x2F;a&gt;. Simply select EKS, configure a few cluster options, and GitLab will automatically provision the cluster correctly and prepare it so you can easily deploy your applications to it. GitLab eliminates the need to manually perform the complex task of cluster creation.&lt;&#x2F;p&gt;

&lt;p&gt;This feature is behind a feature flag and enabled in GitLab.com.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;provision-multicloud-managed-services-with-crossplane&quot;&gt;Provision multicloud managed services with Crossplane&lt;&#x2F;h3&gt;

&lt;p&gt;Building on our commitment to operational efficiency, we’re thrilled to announce that &lt;a href=&quot;#crossplane-support-in-gitlab-managed-apps&quot;&gt;Crossplane is integrated and deployable as a GitLab Managed App&lt;&#x2F;a&gt;. Crossplane removes the friction and effort of provisioning and managing cloud service dependencies by allowing admins to declaratively provision and securely consume managed services from the cloud of your choice, including GCP, AWS, and Azure. Integration with Auto DevOps makes spinning up hosted resources on the cloud as simple as declaring a CI variable.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;view-environment-status-at-a-glance&quot;&gt;View environment status at a glance&lt;&#x2F;h3&gt;

&lt;p&gt;You&#x27;re faced with frequent application changes, all making their way toward production. It’s hard to track changes as they flow through your various dev, staging and prod environments. GitLab&#x27;s new &lt;a href=&quot;#environments-dashboard&quot;&gt;Environments Dashboard&lt;&#x2F;a&gt; surfaces that information, providing a single point of access to the status of environments in all groups and projects. This means you can identify and triage problems (for example, “Is an environment not working because code is being deployed, or because it’s actually broken?”) quickly and visually.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h3&gt;

&lt;p&gt;12.5 is a big release, and there’s a lot more to see. Highlights include &lt;a href=&quot;#code-intelligence-powered-by-sourcegraph&quot;&gt;Sourcegraph integration&lt;&#x2F;a&gt; and a host of new security improvements. Read on to get the details!&lt;&#x2F;p&gt;

&lt;p&gt;We’d love to meet you in person. If you&#x27;re coming to AWS re:Invent December 2 - 6, visit us at booth #1620. Also, &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;registration&lt;&#x2F;a&gt; is now open for the next &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;GitLab Commit User Conference&lt;&#x2F;a&gt; in San Francisco, January 14.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_5&#x2F;12_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.4 released with improved Merge Request Dependencies and Audit API</title>
<release>12.4</release>
<link href='https://about.gitlab.com/releases/2019/10/22/gitlab-12-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/10/22/gitlab-12-4-released/</id>
<published>2019-10-22T00:00:00+00:00</published>
<author>
<name>Fabian Zimmer</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.4 is released with several improvements for governance including an Audit API, Code Owner approvals for Protected Branches, and Access Control for Pages. Merge Request Dependencies help you orchestrate work across teams, while so many more exciting features help you be more efficient and deliver better software faster!&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;merge-request-dependencies&quot;&gt;Merge Request Dependencies&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab can help you improve visibility, collaboration, and productivity. When developers work together to achieve a larger goal, their small changes often need to be merged in a specific sequence to work as intended. To simplify this, &lt;a href=&quot;#merge-request-dependencies&quot;&gt;Merge Request Dependencies&lt;&#x2F;a&gt; allow dependencies to be defined in merge requests, preventing changes from being merged in the wrong order while also improving the visibility of dependencies during code review. This feature was introduced as &lt;em&gt;Cross-Project&lt;&#x2F;em&gt; Merge Request Dependencies in &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;08&#x2F;22&#x2F;gitlab-12-2-released&#x2F;#cross-project-merge-request-dependencies&quot;&gt;12.2&lt;&#x2F;a&gt; but has been renamed to &lt;em&gt;Merge Request Dependencies&lt;&#x2F;em&gt;, and expanded to support more types of dependencies. This includes both cross-project and Merge Request Dependencies within &lt;em&gt;the same&lt;&#x2F;em&gt; project.&lt;&#x2F;p&gt;

&lt;p&gt;We recognize governance is important to you. Here are a few of the key features in 12.4 that will make governance easier for you.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;audit-events-api&quot;&gt;Audit Events API&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab helps you achieve end-to-end visibility across your development lifecycle while streamlining processes. To facilitate this, GitLab &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;product&#x2F;categories&#x2F;gitlab-the-product&#x2F;#plays-well-with-others&quot;&gt;plays well with others&lt;&#x2F;a&gt; and, in 12.4, is introducing an API for instance-level audit events. &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;audit_events.html&quot;&gt;Audit Events&lt;&#x2F;a&gt; are a powerful way to better understand adherance to policies. Using the new &lt;a href=&quot;#audit-events-api&quot;&gt;Audit Events API&lt;&#x2F;a&gt;, administrators can obtain events programmatically and better enable powerful alerting and monitoring that meets specific needs.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;pages-access-control-on-gitlabcom&quot;&gt;Pages Access Control on GitLab.com&lt;&#x2F;h3&gt;

&lt;p&gt;Access control for &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;user&#x2F;project&#x2F;pages&#x2F;&quot;&gt;Pages&lt;&#x2F;a&gt; has been &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-foss&#x2F;issues&#x2F;33422&quot;&gt;available for self-managed&lt;&#x2F;a&gt; but is now &lt;a href=&quot;#access-control-for-pages-is-now-enabled-on-gitlabcom&quot;&gt;available on GitLab.com&lt;&#x2F;a&gt;. It allows an authorized administrator to restrict access to a Pages site or make it available to the public. This is a community contribution that we are very excited to have enabled on GitLab.com!&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;code-owner-approvals-for-protected-branches&quot;&gt;Code Owner Approvals for Protected Branches&lt;&#x2F;h3&gt;

&lt;p&gt;Another feature to aid in governance is the new &lt;a href=&quot;#code-owner-approvals-for-protected-branches&quot;&gt;Code Owner Approvals for Protected Branches&lt;&#x2F;a&gt;. Using merge request approvals to restrict how code is pushed to protected branches is helpful for promoting code quality and implementing compliance controls. However, not all merge requests target stable branches, and not all stable branches need the same controls. In GitLab 12.4, it is possible to prevent directly pushing changes to files or merging changes without the code owner&#x27;s approval for specific branches.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h3&gt;

&lt;p&gt;There are so many great features within GitLab 12.4 that we couldn’t possibly highlight them all. A few favorites include &lt;a href=&quot;#notifications-for-releases&quot;&gt;Notifications for Releases&lt;&#x2F;a&gt;, the ability to &lt;a href=&quot;#view-pod-logs-from-any-environment&quot;&gt;View Pod Logs from Any Environment&lt;&#x2F;a&gt;, and &lt;a href=&quot;#private-project-support-for-online-view-of-html-artifacts&quot;&gt;Private Project Support for Online View of HTML Artifacts&lt;&#x2F;a&gt;. Keep reading below to get details on every feature!&lt;&#x2F;p&gt;

&lt;p&gt;Be sure to catch the &lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=YUXeodJgke0&quot;&gt;recap&lt;&#x2F;a&gt; of our first European user conference from October 9th. The next &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;GitLab Commit User Conference&lt;&#x2F;a&gt; will be in San Francisco in January. &lt;a href=&quot;https:&#x2F;&#x2F;www.eventbrite.com&#x2F;e&#x2F;gitlab-commit-2020-san-francisco-tickets-73836706577&quot;&gt;Registration&lt;&#x2F;a&gt; is now open.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_4&#x2F;12_4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.3 released with Web Application Firewall and Productivity Analytics</title>
<release>12.3</release>
<link href='https://about.gitlab.com/releases/2019/09/22/gitlab-12-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/09/22/gitlab-12-3-released/</id>
<published>2019-09-22T00:00:00+00:00</published>
<author>
<name>Kai Armstrong</name>
</author>
<content type='html'>&lt;p&gt;This month&#x27;s release of GitLab 12.3 is especially exciting following an eventful week in which we hosted our first GitLab Users Conference in Brooklyn New York and announced the completion of a &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-series-e-funding&#x2F;&quot;&gt;$268 million Series E round of fundraising&lt;&#x2F;a&gt;; which will enable us to invest in making all of our DevOps platform offerings, including monitoring, security, and planning, best in class.&lt;&#x2F;p&gt;
&lt;h2 class=&quot;intro-header&quot; id=&quot;web-application-firewall&quot;&gt;Web Application Firewall&lt;&#x2F;h2&gt;

&lt;p&gt;Modern web applications are exposed to new risk from many places, including potentially every client that connects and sends traffic. A Web Application Firewall (WAF) provides monitoring and rules to protect applications in production.  In GitLab 12.3 we are shipping our first iteration of a &lt;a href=&quot;#web-application-firewall-for-kubernetes-ingress&quot;&gt;Web Application Firewall&lt;&#x2F;a&gt; built into the GitLab SDLC platform. Its focus is on monitoring and reporting of security concerns related to your Kubernetes clusters. Future releases will expand the WAF capabilities to block malicious traffic, create and manage firewall rules, and inform earlier stages of development to take action to further reduce risk.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;productivity-analytics---first-release&quot;&gt;Productivity Analytics - First Release&lt;&#x2F;h3&gt;

&lt;p&gt;Software delivery teams everywhere need the right information and insight in order to improve their productivity and efficiency. Too often, invisible bottlenecks and roadblocks force teams to wait and waste time rather than delivering new features. Beginning with 12.3, we’re starting to release new analytics features to help teams and leaders better understand their overall productivity and effectiveness for both Groups and Projects. &lt;a href=&quot;#productivity-analytics&quot;&gt;Productivity Analytics&lt;&#x2F;a&gt; will help teams and their leaders discover best practices to improve productivity. Initially focusing on the time it takes to merge MRs, GitLab will make it possible to drill into the data and learn insight that can guide future improvements. In many organizations, leaders are responsible for multiple projects and &lt;a href=&quot;#analytics-workspace&quot;&gt;Group level analytics workspace&lt;&#x2F;a&gt; is intended to provide productivity and performance insight and visibility across multiple projects. These two features are only the first in a series of updates that will specifically improve visibility and insight so that teams can become more efficient.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;enhanced-compliance&quot;&gt;Enhanced Compliance&lt;&#x2F;h3&gt;

&lt;p&gt;Compliance with policies and procedures is a common challenge that software teams face. For many GitLab users, having development teams collaborate in a single application makes compliance easier. In this 12.3 release of GitLab, we&#x27;re including several features that will continue to streamline efforts to reduce compliance risks. &lt;a href=&quot;#leverage-merge-request-approvals-to-prevent-merging-prohibited-licenses-mvc&quot;&gt;MR approval rules&lt;&#x2F;a&gt; provides a way to prevent teams from merging in code that introduces unsupported licenses. &lt;a href=&quot;#api-to-require-merge-request-approval-by-code-owners-per-branch&quot;&gt;Require code owner approval per branch&lt;&#x2F;a&gt; makes it possible to protect branches and require code owner approval of changes.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h3&gt;

&lt;p&gt;There are so many great features within GitLab 12.3 that we couldn’t possibly highlight them all (even though we really want to). Better resource visibility with &lt;a href=&quot;#global-view-for-group-level-cluster-deploymentsenvironments&quot;&gt;Global view for group-level cluster deployments&#x2F;environments&lt;&#x2F;a&gt;, more efficient Git fetches with &lt;a href=&quot;#compress-git-ref-advertisements-over-http&quot;&gt;Compress Git ref advertisements over HTTP&lt;&#x2F;a&gt;, and more efficient reviews with &lt;a href=&quot;#keyboard-shortcut-for-next-and-previous-unresolved-discussion&quot;&gt;Keyboard Shortcut for Next and Previous Unresolved Discussion&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

&lt;p class=&quot;alert alert-info text-center&quot;&gt;Register now to join us at our first &lt;a href=&quot;&#x2F;events&#x2F;&quot;&gt;European user conference in London on Oct 9!&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_3&#x2F;12_3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.2 released with Directed Acyclic Graphs for Pipelines and Design Management</title>
<release>12.2</release>
<link href='https://about.gitlab.com/releases/2019/08/22/gitlab-12-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/08/22/gitlab-12-2-released/</id>
<published>2019-08-22T00:00:00+00:00</published>
<author>
<name>Joshua Lambert</name>
</author>
<content type='html'>&lt;p&gt;GitLab 12.2 is an exciting release that will help teams optimize their pipelines, improve collaboration, and manage interdependencies between projects. Read on to learn more.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;faster-more-flexible-pipelines&quot;&gt;Faster, more flexible pipelines&lt;&#x2F;h2&gt;

&lt;p&gt;The goal of CI pipelines are to automate manual build and testing tasks, accelerating software delivery while reducing errors and mistakes. However for some use cases, GitLab CI&#x2F;CD pipelines are not as efficient as they could be. With GitLab 12.2, we now support &lt;a href=&quot;#directed-acyclic-graphs-dag-for-gitlab-pipelines&quot;&gt;Directed Acyclic Graphs (DAG)&lt;&#x2F;a&gt; as a method to create and manage detailed job dependencies, rather than relying on sequential stages. This is incredibly powerful and makes it possible for your CI pipelines to become both &lt;strong&gt;faster&lt;&#x2F;strong&gt; and more &lt;strong&gt;efficient&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;design-management&quot;&gt;Design Management&lt;&#x2F;h2&gt;

&lt;p&gt;Software development is a team sport, and our goal is to make it easy for everyone to contribute. In 12.2, we’re delivering new capabilities to include designers and design management in GitLab. &lt;a href=&quot;#annotations-for-designs&quot;&gt;Design Management&lt;&#x2F;a&gt; will make it easy to share, version, and collaborate on design artifacts, helping teams to be more efficient with a single source of truth.&lt;&#x2F;p&gt;

&lt;p&gt;This is just the beginning of focusing on designer specific workflows inside of GitLab and we&#x27;d love for you to contribute to our &lt;a href=&quot;https:&#x2F;&#x2F;about.gitlab.com&#x2F;direction&#x2F;plan&#x2F;&quot;&gt;Design Management Strategy&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;cross-project-merge-request-dependencies&quot;&gt;Cross Project Merge Request Dependencies&lt;&#x2F;h2&gt;

&lt;p&gt;Complex systems often span multiple projects with interdependencies between code changes, where the sequence of merging changes matters. GitLab now supports &lt;a href=&quot;#cross-project-merge-request-dependencies&quot;&gt;Cross-project Merge Request Dependencies&lt;&#x2F;a&gt;, making it possible to define these dependency relationships and prevent mistakes due to changes being merged in the wrong order. Fewer mistakes mean you’re able to reduce rework, and deploy your changes faster.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;There are so many great features within GitLab 12.2 that
we couldn’t possibly highlight them all. &lt;a href=&quot;#restrict-group-membership-by-domain&quot;&gt;Restrict group membership by domain&lt;&#x2F;a&gt;, &lt;a href=&quot;#percent-rollout-strategy-for-feature-flags&quot;&gt;Feature Flag Percent Rollout Strategy and Feature Flag User ID rollout Strategy&lt;&#x2F;a&gt;, &lt;a href=&quot;#security-approval-in-merge-requests&quot;&gt;Security approval in Merge Requests&lt;&#x2F;a&gt;, and now &lt;a href=&quot;#scoped-environment-variables-feature-moved-to-core&quot;&gt;scoped environment variables being included in Core&lt;&#x2F;a&gt;. Keep reading below to get details on every feature!&lt;&#x2F;p&gt;

&lt;p class=&quot;alert alert-info text-center&quot;&gt;&lt;a href=&quot;&#x2F;events&#x2F;&quot;&gt;Register now to join us at our first user conferences in Brooklyn and London!&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_2&#x2F;12_2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.1 released with Parallel Merge Trains and Merge Requests for Confidential Issues</title>
<release>12.1</release>
<link href='https://about.gitlab.com/releases/2019/07/22/gitlab-12-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/07/22/gitlab-12-1-released/</id>
<published>2019-07-22T00:00:00+00:00</published>
<author>
<name>Luca Williams</name>
</author>
<content type='html'>&lt;p&gt;With GitLab 12.1 we are excited to announce new features
that are unique to GitLab, such as Parallel Merge Trains
and Merge Requests for Confidential issues - along with
long-awaited features like managed Let&#x27;s Encrypt certificates
for GitLab Pages. Read on to learn more!&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;keep-the-master-branch-green-at-high-velocity&quot;&gt;Keep the master branch green at high velocity&lt;&#x2F;h2&gt;

&lt;p&gt;Keeping the master branch green is critical for Continuous Delivery. When the production build breaks, it means your new code isn&#x27;t going live, which impacts users and revenue. The only way to be 100% sure the master branch stays green when new code merges is to run the pipeline using the latest version of the master branch. For teams that have a high volume of merges, this can be difficult or even impossible. In the time it takes the pipeline to complete on one code change, other changes can get merged to master with the potential for conflict. The only way to mitigate this is to queue and sequence the changes so that once a production pipeline starts, other code doesn&#x27;t get merged ahead of that change. This is why we came up with &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;merge_request_pipelines&#x2F;pipelines_for_merged_results&#x2F;merge_trains&#x2F;index.html&quot;&gt;Merge Trains&lt;&#x2F;a&gt;, and shipped the &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;06&#x2F;22&#x2F;gitlab-12-0-released&#x2F;#sequential-merge-trains&quot;&gt;first iteration&lt;&#x2F;a&gt;
in Gitlab 12.0.&lt;&#x2F;p&gt;

&lt;p&gt;Merge Trains make use of GitLab&#x27;s &quot;&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;merge_request_pipelines&#x2F;pipelines_for_merged_results&#x2F;index.html&quot;&gt;Pipelines for Merged Results&lt;&#x2F;a&gt;&quot; feature. With Pipelines for Merged Results enabled, GitLab automatically creates a separate ref that contains the result of merging the source and target branch. The Merge Request pipeline runs on that result ref rather than just running on the source branch. This way, you know if your code is safe to merge into master or not without needing to rebase continually.&lt;&#x2F;p&gt;

&lt;p&gt;Building on this functionality, Merge Trains then make sure that merges are put in the proper order once they are set to merge into the target branch. The &lt;strong&gt;merge&lt;&#x2F;strong&gt; button in the MR is replaced with a &lt;strong&gt;start&#x2F;add to merge train&lt;&#x2F;strong&gt; button that adds that merge to the Merge Train queue. Merges are processed in the proper order even if they are coming in at a rapid pace.&lt;&#x2F;p&gt;

&lt;p&gt;Initially, Merge Train pipelines executed sequentially. The previous MR
in the train needed to complete before the pipeline for the next
MR would start, this kept master green, but could slow
things down, especially for projects with long-running pipelines.
Now with GitLab 12.1, we’ve improved Merge Trains to
&lt;a href=&quot;#parallel-execution-strategy-for-merge-trains&quot;&gt;run in parallel&lt;&#x2F;a&gt;.
Up to four pipelines execute simultaneously including the ref from the previous Merge Request in the train based on the assumption that all
previous Merge Request succeeds. This way, the pipelines only need to re-run if a previous Merge Request fails. Executing Merge Train pipelines in parallel significantly speeds up the process. You can get started with Merge Trains today by enabling Pipelines for Merged Results and enjoy CD with an always-green master branch.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;iterate-privately-on-sensitive-updates&quot;&gt;Iterate privately on sensitive updates&lt;&#x2F;h2&gt;

&lt;p&gt;Working publicly in the open is a powerful vehicle for collaboration.
Open source projects with public code, and issue trackers know the benefits of enabling people to contribute regardless of their location. At GitLab we think transparency grants so many benefits that we don’t just make our issues and code public,
but our &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;values&#x2F;#transparency&quot;&gt;business processes&lt;&#x2F;a&gt;
as well.&lt;&#x2F;p&gt;

&lt;p&gt;Alongside all the things that work great when they are out in
the open are &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;communication&#x2F;confidentiality-levels&#x2F;#not-public&quot;&gt;a few things that are better kept private&lt;&#x2F;a&gt;. A typical scenario for many public projects is the need to keep security vulnerabilities private while they are being worked on to mitigate risk. Previously, GitLab supported
Confidential Issues in public projects but if you wanted to
create a confidential merge request you needed to coordinate
in a separate, private code repository.&lt;&#x2F;p&gt;

&lt;p&gt;Now, &lt;a href=&quot;#merge-requests-for-confidential-issues&quot;&gt;Merge Requests for Confidential Issues&lt;&#x2F;a&gt; is making this a lot easier. Clicking on the
&lt;strong&gt;Create Confidential Merge Request&lt;&#x2F;strong&gt; button on a Confidential Issue allows users to select a private fork within which to create the new branch and merge request, this keeps everything under wraps until
it’s appropriate to reveal it by merging the code from the private
fork back into the upstream public project.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;get-automatic-https-certs-for-pages-using-lets-encrypt&quot;&gt;Get automatic HTTPS certs for Pages using Let’s Encrypt&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab Pages is a great way to publish web content, from landing
pages and documentation to project artifacts and reports. Of course,
securing your traffic with HTTPS is a must, but keeping track of
the process to procure, provision, and renew certs can be daunting.
It&#x27;s even more challenging if you are managing a large number of domains. Not having built-in, supported certificate management meant that many organizations operating at scale wanted to use GitLab Pages, but couldn&#x27;t.&lt;&#x2F;p&gt;

&lt;p&gt;Many of you in the GitLab community have told us how valuable
&lt;a href=&quot;#automatic-https-for-pages-with-lets-encrypt&quot;&gt;automated Let’s Encrypt certificates for GitLab Pages&lt;&#x2F;a&gt; would be.
Today, we’re happy to say this highly-requested feature is
available for use. Now, getting secured web traffic to all of
your GitLab Pages custom domains and subdomains is as simple as
clicking a toggle in your Pages settings.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;There are such a lot of great features shipping with GitLab 12.1 that
we couldn’t possibly highlight them all. &lt;a href=&quot;#git-object-deduplication&quot;&gt;Git object deduplication&lt;&#x2F;a&gt;, and Deploy Boards for Kubernetes clusters
at the &lt;a href=&quot;#deploy-boards-for-group-level-kubernetes-clusters&quot;&gt;Group&lt;&#x2F;a&gt;
and &lt;a href=&quot;#deploy-boards-for-instance-level-kubernetes-clusters&quot;&gt;Instance&lt;&#x2F;a&gt; level are just a few of the improvements in this release. Keep reading below to get details on every feature along with links to the docs.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_1&#x2F;flamducks.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 12.0 released with Visual Reviews and Dependency List</title>
<release>12.0</release>
<link href='https://about.gitlab.com/releases/2019/06/22/gitlab-12-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/06/22/gitlab-12-0-released/</id>
<published>2019-06-22T00:00:00+00:00</published>
<author>
<name>Jeremy Watson</name>
</author>
<content type='html'>&lt;h2 id=&quot;dev-sec-and-ops&quot;&gt;Dev, Sec, and Ops&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab 12.0 marks a key step in our journey to create an inclusive approach to
DevSecOps, empowering &quot;everyone to contribute&quot;.&lt;&#x2F;p&gt;

&lt;p&gt;For the past year, we&#x27;ve been on an amazing journey, collaborating and creating
a solution that brings teams together. There have been thousands of community
contributions making GitLab more lovable.&lt;&#x2F;p&gt;

&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;embed&#x2F;sboJfUylJFA&quot; frameborder=&quot;0&quot; allow=&quot;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&quot; allowfullscreen=&quot;&quot;&gt;&lt;&#x2F;iframe&gt;

&lt;p&gt;We believe everyone can contribute, and we’ve enabled cross-team collaboration,
faster delivery of great code, and bringing together Dev, Ops, and Security.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header&quot; id=&quot;visual-reviews&quot;&gt;Visual Reviews&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab review applications are a fantastic tool to enable stakeholders from
Operations to QA to business owners to evaluate and approve application changes
before production.&lt;&#x2F;p&gt;

&lt;p&gt;In GitLab 12.0, &lt;a href=&quot;#visual-reviews&quot;&gt;we make it easy to provide visual feedback&lt;&#x2F;a&gt;
directly from the review app. It’s simple and streamlined, no toggling between
different tabs and typing your feedback, helping to shorten review cycles and
accelerate delivery.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;project-dependency-list&quot;&gt;Project Dependency List&lt;&#x2F;h3&gt;

&lt;p&gt;Projects typically include dozens of individual components, which can introduce
vulnerabilities. Often, security and compliance teams need to be aware of the
specific components included in a project.&lt;&#x2F;p&gt;

&lt;p&gt;Now, we&#x27;re making it &lt;a href=&quot;#project-dependency-list&quot;&gt;easy to view a project&#x27;s dependencies&lt;&#x2F;a&gt;
in a single source of truth.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;limit-access-based-on-ip-address&quot;&gt;Limit access based on IP address&lt;&#x2F;h3&gt;

&lt;p&gt;Some organizations want to limit access to their repositories based on
 specific IP addresses.&lt;&#x2F;p&gt;

&lt;p&gt;In GitLab 12.0, &lt;a href=&quot;#restrict-access-by-ip-address&quot;&gt;you can specifically prohibit&lt;&#x2F;a&gt;
 traffic from outside IP addresses from accessing your GitLab data.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;12_0&#x2F;12_0-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.11 released with Multi-Assignment for MRs and container enhancements</title>
<release>11.11</release>
<link href='https://about.gitlab.com/releases/2019/05/22/gitlab-11-11-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/05/22/gitlab-11-11-released/</id>
<published>2019-05-22T00:00:00+00:00</published>
<author>
<name>Jason Yavorska</name>
</author>
<content type='html'>&lt;h2 id=&quot;increased-collaboration-and-visibility&quot;&gt;Increased collaboration and visibility&lt;&#x2F;h2&gt;

&lt;p&gt;One of the areas we focus on at GitLab is to find new ways to increase collaboration throughout the entire DevOps lifecycle. In this release, we&#x27;re happy to announce that we now support &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#multiple-assignees-for-merge-requests&quot;&gt;Multiple Assignees for a Merge Request&lt;&#x2F;a&gt;! This is available in GitLab Starter and truly embodies our &lt;strong&gt;everyone can contribute&lt;&#x2F;strong&gt; motto. We know that many people may be working&#x2F;collaborating in the same merge request to make sure things are on track, and Multiple Assignees for Merge Requests provides an environment to do just that!&lt;&#x2F;p&gt;

&lt;p&gt;Additionally, we have heightened the visibility for DevOps teams by supporting &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#deployment-notifications-for-slack-and-mattermost&quot;&gt;automated deployment event notifications for Slack and Mattermost&lt;&#x2F;a&gt;. Adding to the list of push events for these two collaborative environments allows a notification to kick off near real-time to update your team every time a deployment occurs.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;reduce-overhead-with-windows-support-of-docker-containers-and-provisioning-instance-level-kubernetes-clusters&quot;&gt;Reduce overhead with Windows support of Docker containers and provisioning instance-level Kubernetes clusters&lt;&#x2F;h2&gt;

&lt;p&gt;We 💖 containers! Containers require fewer system resources than your traditional or virtual machine environments while increasing the portability of your application. With GitLab 11.11, we now support a &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#windows-container-executor-for-gitlab-runner&quot;&gt;Windows Container Executor for GitLab Runners&lt;&#x2F;a&gt;, something that will enable the use of Docker containers on Windows, allowing for more advanced pipeline orchestration and management.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab Premium (self-managed instances only) now has a &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#caching-dependency-proxy-for-container-registry&quot;&gt;Caching Dependency Proxy for your Docker images&lt;&#x2F;a&gt;. This MVC iteration helps to speed up time to delivery by providing a caching proxy for frequently used Docker images.&lt;&#x2F;p&gt;

&lt;p&gt;Users of self-managed GitLab instances are now able to provision an &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#instance-level-kubernetes-cluster-configuration&quot;&gt;Instance Level Kubernetes Cluster&lt;&#x2F;a&gt;, enabling all groups and projects in the instance to make use of it for their deployments. This GitLab Kubernetes integration will automatically create project-specific resources for added security.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h2&gt;

&lt;p&gt;In addition to increased collaboration and visibility capabilities, we&#x27;ve also added &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#guest-access-to-releases&quot;&gt;Guest Access to Releases&lt;&#x2F;a&gt;, extended the &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#add-on-ci-runner-minutes-have-been-extended-to-free-plans&quot;&gt;Add-on CI Runner minutes to GitLab Free&lt;&#x2F;a&gt;, simplified reviews by &lt;a href=&quot;&#x2F;releases&#x2F;2019&#x2F;05&#x2F;22&#x2F;gitlab-11-11-released&#x2F;#applying-a-suggestion-now-automatically-resolves-the-discussion&quot;&gt;auto-resolving a discussion whenever a suggestion is applied&lt;&#x2F;a&gt;, and much more!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_11&#x2F;11_11-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.10 released with Pipelines on the Operations Dashboard, Pipelines for Merged Results, and Multi-line Merge Request Suggestions</title>
<release>11.10</release>
<link href='https://about.gitlab.com/releases/2019/04/22/gitlab-11-10-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/04/22/gitlab-11-10-released/</id>
<published>2019-04-22T00:00:00+00:00</published>
<author>
<name>Eric Brinkman</name>
</author>
<content type='html'>&lt;h3 id=&quot;easily-see-pipeline-health-across-projects&quot;&gt;Easily see pipeline health across projects&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab continues to add features to provide visibility into
the DevOps lifecycle. This release enhances the
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;operations_dashboard&#x2F;&quot;&gt;Operations Dashboard&lt;&#x2F;a&gt;
with a powerful feature that provides an overview of pipeline status.&lt;&#x2F;p&gt;

&lt;p&gt;This is handy even when looking at a single project&#x27;s pipeline,
but is especially valuable when using &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;multi_project_pipelines.html&quot;&gt;multi-project pipelines&lt;&#x2F;a&gt; - common
when you have a microservices architecture and you
need to run a pipeline to test and deploy code housed in
multiple different project repositories. Now you can get
instant visibility at a glance into the health of all of
your &lt;a href=&quot;#pipelines-on-the-operations-dashboard&quot;&gt;pipelines on the Operations Dashboard&lt;&#x2F;a&gt;,
no matter where they run.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;run-pipelines-against-merged-results&quot;&gt;Run pipelines against merged results&lt;&#x2F;h3&gt;

&lt;p&gt;Over time it’s possible for your source and target branches to diverge, 
which can result in the scenario where both source and target pipelines pass, 
but the combined output fails. Now, you can &lt;a href=&quot;#pipelines-for-merged-results&quot;&gt;run pipelines against the merged result&lt;&#x2F;a&gt;
prior to merging. This allows you to quickly catch errors that would only
surface if you had rebased often, allowing for much quicker resolution of pipeline failures 
and more efficient usage of &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;runner&#x2F;&quot;&gt;GitLab Runners&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;further-streamline-collaboration&quot;&gt;Further streamline collaboration&lt;&#x2F;h3&gt;

&lt;p&gt;With GitLab 11.10, we provide even more features to simplify
collaboration and developer workflows. In a &lt;a href=&quot;&#x2F;releases&#x2F;2018&#x2F;12&#x2F;22&#x2F;gitlab-11-6-released&#x2F;#suggested-changes&quot;&gt;previous release&lt;&#x2F;a&gt;,
we introduced merge request suggestions, allowing a reviewer
to suggest a one-line change in a merge request comment that
can be readily committed from within the comment thread
interface. Our users loved it and wanted more. Now, you can
suggest a &lt;a href=&quot;#suggest-changes-to-multiple-lines&quot;&gt;multi-line change&lt;&#x2F;a&gt;,
specifying which existing lines to remove, and introducing multiple
lines of additions. Thank you for contributing improvement suggestions!&lt;&#x2F;p&gt;

&lt;h3 id=&quot;and-so-much-more&quot;&gt;And so much more…&lt;&#x2F;h3&gt;

&lt;p&gt;So many great features are available in this release, like
&lt;a href=&quot;#scoped-labels&quot;&gt;Scoped Labels&lt;&#x2F;a&gt;,
a more thorough &lt;a href=&quot;#more-thorough-container-registry-cleanup&quot;&gt;Container Registry cleanup&lt;&#x2F;a&gt;,
&lt;a href=&quot;#composable-auto-devops&quot;&gt;Composable Auto DevOps&lt;&#x2F;a&gt;,
and the ability to &lt;a href=&quot;#purchase-add-on-ci-runner-minutes&quot;&gt;purchase additional CI Runner minutes&lt;&#x2F;a&gt;.
Read on to learn about them all!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_10&#x2F;11_10-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.9 released with secrets detection and multiple MR approval rules</title>
<release>11.9</release>
<link href='https://about.gitlab.com/releases/2019/03/22/gitlab-11-9-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/03/22/gitlab-11-9-released/</id>
<published>2019-03-22T00:00:00+00:00</published>
<author>
<name>Kenny Johnston</name>
</author>
<content type='html'>&lt;h3 id=&quot;quickly-learn-if-secrets-have-been-leaked&quot;&gt;Quickly learn if secrets have been leaked&lt;&#x2F;h3&gt;

&lt;p&gt;Inadvertently committing credentials to a shared repository can have serious consequences, yet it is a simple
mistake to make. Once an attacker gets your password or API key, they can take over your account, lock you out, and fraudulently spend money.
This can even lead to a domino effect where access to one account grants access to others. With the stakes so high,
it’s of paramount importance to learn as quickly as possible if secrets have been leaked.&lt;&#x2F;p&gt;

&lt;p&gt;With this release, we’re introducing &lt;a href=&quot;#detect-secrets-and-credentials-in-the-repository&quot;&gt;secret detection&lt;&#x2F;a&gt; as
part of our SAST functionality. Each commit is scanned by a CI&#x2F;CD job to ensure it doesn’t contain secrets.
If the scan detects secrets, the developer is alerted in the merge request, allowing them to take action quickly
to invalidate the leaked credentials and generate new ones.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;enforce-proper-change-management&quot;&gt;Enforce proper change management&lt;&#x2F;h3&gt;

&lt;p&gt;As an organization grows and becomes more complex, it becomes difficult to keep alignment across different
parts of the organization. At the same time, the consequences of merging improper or insecure code also
increase when an application has more users and generates more revenue. For many organizations, ensuring
proper review process is followed before code is merged is a hard requirement because the risks of not doing so are so great.&lt;&#x2F;p&gt;

&lt;p&gt;With GitLab 11.9, we’re providing greater controls and more structure with &lt;a href=&quot;#merge-request-approval-rules&quot;&gt;Merge request approval rules&lt;&#x2F;a&gt;.
Previously, you could specify either an individual or a group for required approval (where any single member of the group can provide approval). Now, multiple rules can be added to a merge request to require individual approvers specifically,
or even require a number of approvers from a particular group. Additionally, the Code Owners feature is an integrated part of approval rules, making it easy to track down who should approve.&lt;&#x2F;p&gt;

&lt;p&gt;This allows organizations to implement complex approval flows, all
while maintaining the simplicity of GitLab’s single application where issues, code, pipelines, and monitoring
data are visible and accessible to inform decisions and speed approval.&lt;&#x2F;p&gt;

&lt;p class=&quot;alert alert-info&quot;&gt;Approval Rules have temporarily been disabled on GitLab.com and are not enabled by default in GitLab 11.9 due to a
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;issues&#x2F;10356&quot;&gt;regression&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;chatops-is-now-open-source&quot;&gt;ChatOps is now open source&lt;&#x2F;h3&gt;

&lt;p&gt;GitLab ChatOps is a powerful automation tool, allowing you to execute any CI&#x2F;CD job and receive the status
of the job directly from chat apps like Slack and Mattermost. Originally &lt;a href=&quot;&#x2F;releases&#x2F;2018&#x2F;03&#x2F;22&#x2F;gitlab-10-6-released&#x2F;#gitlab-chatops-alpha&quot;&gt;released in GitLab 10.6&lt;&#x2F;a&gt;, ChatOps
was part of the GitLab Ultimate tier. As part of our &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;company&#x2F;pricing&#x2F;#the-likely-type-of-buyer-determines-what-features-go-in-what-tier&quot;&gt;product strategy&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;company&#x2F;stewardship&#x2F;&quot;&gt;commitment to open source&lt;&#x2F;a&gt;,
we occasionally move features down in tier and never move them up.&lt;&#x2F;p&gt;

&lt;p&gt;With ChatOps, we felt this was functionality that everyone could benefit from and that the feature itself could benefit from community contributions.&lt;&#x2F;p&gt;

&lt;p&gt;In GitLab 11.9, we’ve &lt;a href=&quot;#move-chatops-to-core&quot;&gt;open sourced ChatOps&lt;&#x2F;a&gt; so it is available to use in GitLab
self-managed Core and GitLab.com Free, and is open for community contributions.&lt;&#x2F;p&gt;

&lt;h3 id=&quot;and-much-more&quot;&gt;And much more!&lt;&#x2F;h3&gt;

&lt;p&gt;So many great features are available in this release like &lt;a href=&quot;#auditing-for-feature-flags&quot;&gt;Auditing for feature flags&lt;&#x2F;a&gt;,
&lt;a href=&quot;#vulnerability-remediation-merge-request&quot;&gt;Vulnerability remediation merge request&lt;&#x2F;a&gt;,
and &lt;a href=&quot;#cicd-templates-for-security-jobs&quot;&gt;CI&#x2F;CD templates for security jobs&lt;&#x2F;a&gt; that you’ll want to read on to learn about them all!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_9&#x2F;11_9-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.8 released with SAST for JavaScript, Pages for subgroups, and Error Tracking</title>
<release>11.8</release>
<link href='https://about.gitlab.com/releases/2019/02/22/gitlab-11-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/02/22/gitlab-11-8-released/</id>
<published>2019-02-22T00:00:00+00:00</published>
<author>
<name>Joshua Lambert</name>
</author>
<content type='html'>&lt;h2 class=&quot;intro-header&quot; id=&quot;javascript-coverage-in-sast&quot;&gt;JavaScript coverage in SAST&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab Static Application Security Testing (SAST) scans source code and helps to detect potential security vulnerabilities early in the pipeline. In 11.8, we&#x27;ve added &lt;a href=&quot;.&#x2F;#sast-support-for-javascript&quot;&gt;SAST support for JavaScript&lt;&#x2F;a&gt;, building on top of our existing node.js support. Now any JavaScript file can be scanned, like static scripts and HTML. A vital practice in DevSecOps is to scan code changes with each commit, and with this change, we&#x27;re covering one of the most popular web languages, helping you to find JavaScript risks as early as possible.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;gitlab-pages-for-subgroups-and-templates&quot;&gt;GitLab Pages for subgroups and templates&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab Pages got a whole lot better this release, with two key improvements. First, we have introduced &lt;a href=&quot;.&#x2F;#pages-support-for-subgroups&quot;&gt;GitLab Pages support for projects in subgroups&lt;&#x2F;a&gt;, enabling these projects to easily publish content to the web. GitLab 11.8 also bundles our most popular &lt;a href=&quot;.&#x2F;#create-pages-sites-in-one-click-using-bundled-templates&quot;&gt;templates for Pages&lt;&#x2F;a&gt;, so users can get started with just a single click.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;error-tracking-with-sentry&quot;&gt;Error Tracking with Sentry&lt;&#x2F;h2&gt;

&lt;p&gt;Application errors provide important insight into the health of your application, and can help detect problems without waiting for users to report them. GitLab 11.8 can now &lt;a href=&quot;.&#x2F;#error-tracking-with-sentry&quot;&gt;display the most recent errors&lt;&#x2F;a&gt; directly within the project, making them easier and quicker to find and take action on.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-many-more-great-features&quot;&gt;And many more great features!&lt;&#x2F;h2&gt;

&lt;p&gt;There are so many great features in this release, that we wanted to highlight a few more:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;.&#x2F;#merge-request-approval-rules&quot;&gt;&lt;strong&gt;Merge Request Approval Rules&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: Easily define rules for who needs to approve a change, whether it&#x27;s a specific user, group, or role. Available on GitLab.com soon, and can be enabled in your own GitLab instance by an administrator.&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;.&#x2F;#feature-flags-for-environments&quot;&gt;&lt;strong&gt;Feature Flags for Environments&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: Previously, feature flags were either on or off across all of your environments. No more! Feature flags can now be selectively enabled on a per-environment basis. Available on GitLab.com today, and can be enabled in your own GitLab instance by an administrator.&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;#improved-squash-commit-messages&quot;&gt;&lt;strong&gt;Improved Squash Commit Messages&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: For those who enjoy crafting great commit messages, it can be sad to see them lost in a squashed commit to keep things tidy. On 11.8 squashed commits now automatically utilize the first multi-line commit message, and can also be overridden to make them even better.&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_8&#x2F;11_8-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.7 shipped with Releases, Multi-level Child Epics, and NPM Registry</title>
<release>11.7</release>
<link href='https://about.gitlab.com/releases/2019/01/22/gitlab-11-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2019/01/22/gitlab-11-7-released/</id>
<published>2019-01-22T00:00:00+00:00</published>
<author>
<name>Victor Wu</name>
</author>
<content type='html'>&lt;h2 class=&quot;intro-header&quot; id=&quot;managing-releases-just-got-a-whole-lot-easier&quot;&gt;Managing releases just got a whole lot easier&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab 11.7 delivers &lt;a href=&quot;#publish-releases-for-your-projects&quot;&gt;Releases&lt;&#x2F;a&gt; in GitLab Core. Users now have release snapshots that not only include the source code but &lt;em&gt;all&lt;&#x2F;em&gt; 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.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;portfolio-management-supports-more-complex-work-breakdown-structures&quot;&gt;Portfolio Management supports more complex work breakdown structures&lt;&#x2F;h2&gt;

&lt;p&gt;&lt;a href=&quot;#multi-level-child-epics&quot;&gt;Multi-level Child Epics&lt;&#x2F;a&gt; 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.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;streamlining-javascript-development-with-npm-registries&quot;&gt;Streamlining JavaScript development with NPM registries&lt;&#x2F;h2&gt;

&lt;p&gt;Gitlab 11.7 Premium delivers &lt;a href=&quot;#npm-registry&quot;&gt;NPM registries&lt;&#x2F;a&gt; 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!&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-so-much-more&quot;&gt;And so much more&lt;&#x2F;h2&gt;

&lt;p&gt;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:&lt;&#x2F;p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;#remediate-vulnerability-with-patch-file&quot;&gt;&lt;strong&gt;Remediate vulnerability with patch file&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: 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!&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;#api-support-for-kubernetes-integration&quot;&gt;&lt;strong&gt;API integration with Kubernetes&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: If you are into creating &lt;em&gt;a lot&lt;&#x2F;em&gt; 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!&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
  &lt;li&gt;
    &lt;p&gt;&lt;a href=&quot;#cross-project-pipeline-browsing&quot;&gt;&lt;strong&gt;Cross-project pipeline browsing&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt;: With the ability to view pipelines across projects, the sky&#x27;s the limit on what information is readily at your fingertips with this feature!&lt;&#x2F;p&gt;
  &lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;

&lt;p&gt;Read on for the complete list of features for GitLab 11.7!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_7&#x2F;11_7-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.6 released with Serverless and Group-level Clusters</title>
<release>11.6</release>
<link href='https://about.gitlab.com/releases/2018/12/22/gitlab-11-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/12/22/gitlab-11-6-released/</id>
<published>2018-12-22T00:00:00+00:00</published>
<author>
<name>James Ramsay</name>
</author>
<content type='html'>&lt;h2 class=&quot;intro-header&quot; id=&quot;deploy-serverless-workloads-to-any-cloud-via-gitlab&quot;&gt;Deploy serverless workloads to any cloud via GitLab&lt;&#x2F;h2&gt;

&lt;p&gt;Serverless computing dynamically allocates cloud resources whenever a piece of code is executed, optimizing allocation and distribution of the resources used to run your code. It is growing in popularity with developers because it allows them to focus on what matters most, namely writing code, without worrying about the underlying information technology infrastructure.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;a href=&quot;&#x2F;topics&#x2F;serverless&#x2F;&quot;&gt;GitLab Serverless&lt;&#x2F;a&gt; uses Knative, a Kubernetes-based platform, to build, deploy, and manage serverless workloads. This feature provides developers with an easy way to build and manage serverless workloads alongside the rest of their code, in a familiar user interface. For businesses, serverless enables a multi-cloud strategy and prevents being locked into a specific cloud provider.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header-h3&quot; id=&quot;gitlab-continues-to-simplify-development-of-cloud-native-applications&quot;&gt;GitLab continues to simplify development of cloud native applications&lt;&#x2F;h2&gt;

&lt;p&gt;With a built-in &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;packages&#x2F;container_registry&#x2F;index.html&quot;&gt;Container Registry&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;clusters&#x2F;index.html&quot;&gt;Kubernetes integration&lt;&#x2F;a&gt;, GitLab makes it easier than ever to get started with containers and cloud native development. With 11.6, users will be able to create &lt;a href=&quot;#kubernetes-clusters-for-groups-beta&quot;&gt;Kubernetes clusters for groups&lt;&#x2F;a&gt; that can be used by all the projects contained within the group or sub-groups. This further simplifies cloud native configuration and allow developers to focus on developing great applications.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header-h3&quot; id=&quot;its-the-holidays-get-excited-weve-stuffed-many-more-features-into-116&quot;&gt;It&#x27;s the holidays! Get excited! We&#x27;ve stuffed many more features into 11.6!&lt;&#x2F;h2&gt;

&lt;p&gt;A few of our favorites include &lt;a href=&quot;#suggested-changes&quot;&gt;Suggested Changes&lt;&#x2F;a&gt;, &lt;a href=&quot;#web-terminal-for-web-ide-beta&quot;&gt;Web Terminal for Web IDE&lt;&#x2F;a&gt;, and the &lt;a href=&quot;#vulnerability-chart-for-group-security-dashboards&quot;&gt;Group Security Dashboard Vulnerability Chart&lt;&#x2F;a&gt;. Team contributions are more easily accepted now that changes suggested (when leaving a comment on a merge request diff) can be accepted with a single click. Also, from the Web IDE, you can now launch a Web Terminal, the first server-side evaluation feature of the popular Web IDE. Building upon &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;security_dashboard&#x2F;&quot;&gt;Group Security Dashboards&lt;&#x2F;a&gt; released last month, the new Vulnerability Chart shows the security team how the number of vulnerabilities is changing day by day to provide resolution metrics.&lt;&#x2F;p&gt;

&lt;p&gt;Read on for all of the holiday goodies delivered with GitLab 11.6!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_6&#x2F;11_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.5 released with Group Security and Operations Dashboards, and Access Control for Pages</title>
<release>11.5</release>
<link href='https://about.gitlab.com/releases/2018/11/22/gitlab-11-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/11/22/gitlab-11-5-released/</id>
<published>2018-11-22T00:00:00+00:00</published>
<author>
<name>Fabio Busatto</name>
</author>
<content type='html'>&lt;h2 class=&quot;intro-header&quot; id=&quot;group-dashboard-for-security-teams&quot;&gt;Group dashboard for security teams&lt;&#x2F;h2&gt;

&lt;p&gt;For a long time, developers have used GitLab as a tool to secure their code. But now,
GitLab is making security teams first-class citizens so they can use GitLab to effect better application security and ensure compliance. With 11.5, the
&lt;a href=&quot;#group-security-dashboard&quot;&gt;Group Security Dashboard&lt;&#x2F;a&gt; pulls together all of the information security personnel need into one place, so folks like CISOs,
CIOs, and application security leaders get a specific view designed for them.
The group dashboard has a redesigned look and new visualizations, bringing together
security information across multiple projects and providing a high-level view while
also enabling the ability to drill down into specific reports. With 11.5, we&#x27;re
starting with SAST reports, and we&#x27;ll be adding more to the group dashboard in
the future. Our goal is to build a single tool that security teams can use
instead of needing to switch back and forth between multiple tools.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;new-dashboard-for-operations-teams&quot;&gt;New dashboard for operations teams&lt;&#x2F;h2&gt;

&lt;p&gt;In the same way that the Group Security Dashboard makes security teams first-class citizens, the &lt;a href=&quot;#operations-dashboard&quot;&gt;Operations Dashboard&lt;&#x2F;a&gt; provides a
tailored experience for operations professionals. This instance-wide dashboard
provides a single view across projects to get a summary of each project’s
operational health, including pipeline and alert status.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;control-access-to-gitlab-pages&quot;&gt;Control access to GitLab Pages&lt;&#x2F;h2&gt;

&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;user&#x2F;project&#x2F;pages&#x2F;&quot;&gt;GitLab Pages&lt;&#x2F;a&gt; is an easy way to
serve static content on the web, making it perfect for use cases such as
documentation for your project. But what about private projects where
documentation and other static artifacts should only be accessed by project
members? In the past, you&#x27;d either have to make your assets public to take
advantage of Pages, or you would not be able to use the feature at all.&lt;&#x2F;p&gt;

&lt;p&gt;Now, in GitLab 11.5, the same access control permissions that apply to your
issues and code can also be applied to static webpages served by GitLab Pages.
Unauthenticated users will get a 404 when visiting the link. As of today,
&lt;a href=&quot;#access-control-for-pages&quot;&gt;access controls for GitLab pages&lt;&#x2F;a&gt; is available for self-managed GitLab,
with GitLab.com support coming soon.&lt;&#x2F;p&gt;

&lt;p&gt;This is a unique feature that we&#x27;re particularly proud of because it comes
from our open source community. Access control for Pages has been one of our
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;33422&quot;&gt;most requested features&lt;&#x2F;a&gt;
and &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-pages&#x2F;merge_requests&#x2F;94&quot;&gt;the code has been community contributed&lt;&#x2F;a&gt; as well!&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;knative-for-kubernetes&quot;&gt;Knative for Kubernetes&lt;&#x2F;h2&gt;

&lt;p&gt;“Serverless” is a popular, yet often misunderstood industry term. Some folks equate
serverless with &quot;Function as a Service,&quot; or FaaS, but this &lt;a href=&quot;https:&#x2F;&#x2F;martinfowler.com&#x2F;articles&#x2F;serverless.html&quot;&gt;isn&#x27;t quite accurate&lt;&#x2F;a&gt;. In a nutshell, serverless enables a programming paradigm where you are able
to focus on writing business logic without having to understand or even
worry about the underlying infrastructure where your software is deployed.
As such, both functions and applications can be serverless.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;cloud.google.com&#x2F;knative&#x2F;&quot;&gt;Knative&lt;&#x2F;a&gt; is a Kubernetes-based platform
to build, deploy, and manage modern serverless workloads, and GitLab 11.5
comes with the ability to &lt;a href=&quot;#easily-deploy-and-integrate-knative-with-gitlab&quot;&gt;easily deploy and integrate Knative with GitLab&lt;&#x2F;a&gt;. You can now install Knative to your &lt;a href=&quot;&#x2F;solutions&#x2F;kubernetes&#x2F;&quot;&gt;connected Kubernetes cluster&lt;&#x2F;a&gt; with a single click. With GitLab 11.5, you&#x27;ll be able to use Knative for your serverless applications, with
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;43959&quot;&gt;serverless functions coming in 11.6&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Today, Knative is still in alpha, but there are some compelling reasons to deploy applications using Knative as it comes with some powerful functionality out-of-the-box. In particular, Knative manages pod scaling for you so you can automatically scale up, or even scale down to zero without additional configuration. Additionally, Knative comes with eventing built in so using it to deploy microservices makes it easier to manage inter-process communication between your producer and consumer services.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;and-so-much-more&quot;&gt;And so much more!&lt;&#x2F;h2&gt;

&lt;p&gt;With so many great features in this release, we couldn&#x27;t pack them all into
the intro. Be sure to read up on other exciting new features like
&lt;a href=&quot;#parallel-attribute-for-faster-pipelines&quot;&gt;the parallel attribute for faster pipelines&lt;&#x2F;a&gt;,
&lt;a href=&quot;#issue-board-cards-redesigned&quot;&gt;redesigned Issue Board cards&lt;&#x2F;a&gt;, and an initial
&lt;a href=&quot;#open-jaeger-from-gitlab&quot;&gt;Jaeger integration&lt;&#x2F;a&gt;.
We’ve made big improvements in this release to make code review easier and more useful, including the ability to
&lt;a href=&quot;#comment-on-unchanged-lines-in-merge-request&quot;&gt;comment on unchanged lines in merge requests&lt;&#x2F;a&gt;,
&lt;a href=&quot;#preview-merge-request-review-before-submitting-it&quot;&gt;preview merge request reviews before submitting&lt;&#x2F;a&gt;, and
&lt;a href=&quot;#assign-approvers-based-on-code-owners&quot;&gt;assign approvers based on Code Owners&lt;&#x2F;a&gt; along with
&lt;a href=&quot;#review-app-direct-link&quot;&gt;Review App direct links&lt;&#x2F;a&gt;.
Keep reading to see all of the features that are part of this release.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_5&#x2F;11_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.4 released with Merge Request Reviews and Feature Flags</title>
<release>11.4</release>
<link href='https://about.gitlab.com/releases/2018/10/22/gitlab-11-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/10/22/gitlab-11-4-released/</id>
<published>2018-10-22T00:00:00+00:00</published>
<author>
<name>James Ramsay</name>
</author>
<content type='html'>&lt;p&gt;We&#x27;re excited to announce the release of GitLab 11.4 with incredible updates to help teams
work together more efficiently. Most teams adopting DevOps are focused on shortening
cycle time, so improvements that reduce waste and extra work are welcome contributions toward
faster delivery and better business results.&lt;&#x2F;p&gt;

&lt;p&gt;With GitLab 11.4 we&#x27;re making code reviews more efficient with
&lt;a href=&quot;#merge-request-reviews&quot;&gt;Merge Request Reviews&lt;&#x2F;a&gt; and a &lt;a href=&quot;#file-tree-for-browsing-merge-request-diff&quot;&gt;file tree for diffs&lt;&#x2F;a&gt;.
We are introducing &lt;a href=&quot;#create-and-toggle-feature-flags-for-your-applications-alpha&quot;&gt;Feature Flags&lt;&#x2F;a&gt; in alpha.
Auto DevOps and CI is more powerful with &lt;a href=&quot;#support-postgresql-db-migration-and-initialization-for-auto-devops&quot;&gt;PostgreSQL migrations&lt;&#x2F;a&gt; and &lt;a href=&quot;#add-timed-incremental-rollouts-to-auto-devops&quot;&gt;timed incremental rollout&lt;&#x2F;a&gt;.
Even Git is faster with support for &lt;a href=&quot;#git-protocol-v2&quot;&gt;Git protocol v2&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;code-review&quot;&gt;Code review&lt;&#x2F;h2&gt;

&lt;p&gt;&lt;a href=&quot;#merge-request-reviews&quot;&gt;Merge Request Reviews&lt;&#x2F;a&gt; will reduce the noise from comments on code and merge requests.
Batch Comments lets a reviewer enter multiple comments on the code or merge request and 
then finalize them in one batch. Now, the people subscribed to the project can more 
efficiently keep track of changes.&lt;&#x2F;p&gt;

&lt;p&gt;Having the right people review and approve code changes is a key step to delivering high-quality code.
Building on Code Owners from the &lt;a href=&quot;&#x2F;releases&#x2F;2018&#x2F;09&#x2F;22&#x2F;gitlab-11-3-released&#x2F;&quot;&gt;11.3 release&lt;&#x2F;a&gt;,
GitLab can now suggest who should review and approve a specific merge request based on the
&lt;code&gt;CODEOWNERS&lt;&#x2F;code&gt; file. This way, you can quickly and efficiently get changes reviewed and approved.
This will also be useful when defining separation of duties and roles on a team, where you want to
have defined reviewers for certain parts of the code.&lt;&#x2F;p&gt;

&lt;p&gt;The addition of the file tree view to the merge request makes it easier and faster for reviewers to
navigate through multiple changed files and then provide their feedback.&lt;&#x2F;p&gt;

&lt;p&gt;Russell Levy, co-founder and CTO of &lt;a href=&quot;http:&#x2F;&#x2F;www.chorus.ai&quot;&gt;Chorus.ai&lt;&#x2F;a&gt;, explains how the reviews and file-tree
view features are helping their team:&lt;&#x2F;p&gt;

&lt;blockquote&gt;
  &lt;p&gt;&lt;em&gt;We&#x27;re pretty thorough in code reviews and there are generally 10-20 comments on
a medium-sized merge request, plus a few rounds of conversations based on it. Using
the review feature reduces the noise and interruptions during the review process.&lt;&#x2F;em&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;em&gt;For larger merge requests, the new file tree and diffs feature makes reviews that
much faster, as it makes it easy to jump around the code to understand dependencies.&lt;&#x2F;em&gt;&lt;&#x2F;p&gt;
&lt;&#x2F;blockquote&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;feature-flags&quot;&gt;Feature flags&lt;&#x2F;h2&gt;

&lt;p&gt;We are introducing an Alpha version of &lt;a href=&quot;#create-and-toggle-feature-flags-for-your-applications-alpha&quot;&gt;Feature Flags&lt;&#x2F;a&gt;, a feature toggle system. Teams can
now practice Continuous Delivery by deploying new features to production in small batches,
mitigating risk before a full rollout.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;auto-devops-and-cicd&quot;&gt;Auto DevOps and CI&#x2F;CD&lt;&#x2F;h2&gt;

&lt;p&gt;We&#x27;re also updating the ability for all users to take advantage of having
&lt;a href=&quot;#move-ability-to-use-includes-in-codegitlab-ciymlcode-from-starter-to-core&quot;&gt;Include files in their &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; files&lt;&#x2F;a&gt;, moving it from Starter to Core. This will make it easier
for all teams to leverage this best practice and more efficiently manage their CI&#x2F;CD pipelines.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;extra-polish&quot;&gt;Extra polish&lt;&#x2F;h2&gt;

&lt;p&gt;Together with the wider GitLab community, there are many more wonderful improvements
we have included in this release including a new profile layout, faster access to
your profile status, highlighted &lt;code&gt;@mentions&lt;&#x2F;code&gt;, new quick actions, and the ability
to close epics.&lt;&#x2F;p&gt;

&lt;p&gt;Read on to learn more about all the great features in GitLab 11.4.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_4&#x2F;11_4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.3 released with Maven Repository and Protected Environments</title>
<release>11.3</release>
<link href='https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/</id>
<published>2018-09-22T00:00:00+00:00</published>
<author>
<name>Daniel Gruesso</name>
</author>
<content type='html'>&lt;p&gt;With our shipment today of GitLab 11.3, we are excited to announce
support for Maven repositories, Code Owners, Protected Environments, and epic forecasting. These features help
automate controls around environments and code while providing further efficiencies for
Java developers.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;maven-repository&quot;&gt;Maven Repository&lt;&#x2F;h2&gt;

&lt;p&gt;We have expanded our support for Java projects and developers by
building &lt;a href=&quot;#maven-repository&quot;&gt;Maven&lt;&#x2F;a&gt; repositories directly into GitLab.
This provides Java developers with a secure, standardized way to share
version control in Maven libraries and save time by reusing
these libraries across projects. This feature is available with GitLab Premium.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;code-owners-and-protected-environments&quot;&gt;Code Owners and Protected Environments&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab Starter now supports the assignment of &lt;a href=&quot;#code-owners&quot;&gt;Code Owners&lt;&#x2F;a&gt; to files
to indicate the appropriate team members responsible for the code. This feature prepares us for futures releases that will enforce
internal controls at the code level.&lt;&#x2F;p&gt;

&lt;p&gt;Available in GitLab Premium, operators can also use &lt;a href=&quot;#protected-environments&quot;&gt;Protected Environments&lt;&#x2F;a&gt;
to set permissions determining who can deploy code to production environments.
This significantly reduces the risk of the wrong person committing something they
shouldn’t and increases overall security of the environment.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;epic-forecasting&quot;&gt;Epic forecasting&lt;&#x2F;h2&gt;

&lt;p&gt;A new Portfolio Management feature in GitLab Ultimate can automatically
&lt;a href=&quot;#epic-forecasting-with-integrated-milestone-dates&quot;&gt;forecast an epic&#x27;s start and end dates&lt;&#x2F;a&gt;
based on the milestone dates of its issues. With this enhancement,
portfolio managers will be able to compare their planned start and end dates against
the work that is scheduled through milestones, gaining visibility into potential
slippage in epic delivery. This will enable faster, better decisions on what can be
delivered and when plans need to be adjusted.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;everyone-can-contribute&quot;&gt;Everyone can contribute&lt;&#x2F;h2&gt;

&lt;p&gt;Many of these improvements were contributed by the greater GitLab community.
We look forward to your feedback and improvements on these great new features.
Together, we make an awesome team! 🏆&lt;&#x2F;p&gt;

&lt;p&gt;Let us know what you think in the comments below. What are you looking
forward to in this release? What can we continue to improve on?&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_3&#x2F;gitlab-11-3-released-cover.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.2 released with live preview in the Web IDE and Android project import</title>
<release>11.2</release>
<link href='https://about.gitlab.com/releases/2018/08/22/gitlab-11-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/08/22/gitlab-11-2-released/</id>
<published>2018-08-22T00:00:00+00:00</published>
<author>
<name>Mike Lewis</name>
</author>
<content type='html'>&lt;p&gt;We are super excited to deliver new features with 11.2 that will help you
get started and iterate faster. Today we deliver enhancements to the Web IDE,
support for manifest files to import Android projects, and enable custom
project templates.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;preview-changes-in-the-web-ide&quot;&gt;Preview changes in the Web IDE&lt;&#x2F;h2&gt;

&lt;p&gt;The Web IDE makes it faster and easier to contribute changes to your projects
by providing an advanced code editor with commit staging right within your
browser. With GitLab 11.2 we’ve made it even easier to see the effect of
your code changes and debug even before you commit. You can now
&lt;a href=&quot;#client-side-evaluation-in-web-ide&quot;&gt;preview your JavaScript web app in the Web IDE&lt;&#x2F;a&gt;,
viewing your changes in real time, right next to the code for client-side evaluation.&lt;&#x2F;p&gt;

&lt;p&gt;In addition, with 11.2, you can delete and rename files and switch branches
without ever leaving the Web IDE.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;android-project-import&quot;&gt;Android project import&lt;&#x2F;h2&gt;

&lt;p&gt;Until now, importing complex project structures with multiple sub-structures
was a tedious, time-consuming task. With our &lt;a href=&quot;#support-for-android-project-import&quot;&gt;new support for XML manifest files&lt;&#x2F;a&gt;,
you can now import larger project structures with multiple repositories altogether,
in bulk, including Android OS code from the &lt;a href=&quot;https:&#x2F;&#x2F;source.android.com&quot;&gt;Android Open Source Project (AOSP)&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;cloud-native-simplified&quot;&gt;Cloud native simplified&lt;&#x2F;h2&gt;

&lt;p&gt;The &lt;a href=&quot;#cloud-native-gitlab-helm-chart-generally-available&quot;&gt;Cloud Native Helm Chart is now generally available&lt;&#x2F;a&gt;
to help you more quickly install GitLab on Kubernetes. This chart features a
more cloud native architecture, with a container for each component of GitLab
and no requirement for shared storage. The result is increased resilience,
scalability, and performance of GitLab on Kubernetes. A
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;runner&#x2F;&quot;&gt;GitLab Runner&lt;&#x2F;a&gt; is also deployed, making it
easy to get started with GitLab CI&#x2F;CD.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;lots-more&quot;&gt;Lots more!&lt;&#x2F;h2&gt;

&lt;p&gt;Several other additions will help you and your teams handle projects more
efficiently. With 11.2, GitLab administrators can offer
&lt;strong&gt;&lt;a href=&quot;#custom-project-templates-on-the-instance-level&quot;&gt;instance-wide custom project templates&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;,
allowing users to start new projects quickly by automating repetitive setup tasks.&lt;&#x2F;p&gt;

&lt;p&gt;At the same time, features such as issue board
&lt;strong&gt;&lt;a href=&quot;#issue-board-milestone-lists&quot;&gt;milestone lists&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;,
&lt;strong&gt;&lt;a href=&quot;#summed-weights-in-issue-board-list&quot;&gt;summed weights&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;
for issue board lists, &lt;strong&gt;&lt;a href=&quot;#group-milestones-on-dashboard-milestones-list-page&quot;&gt;group milestones on the milestone dashboard page&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;,
and &lt;strong&gt;&lt;a href=&quot;#todos-for-epics&quot;&gt;todos for epics&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; enable
better work management.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;everyone-can-contribute&quot;&gt;Everyone can contribute&lt;&#x2F;h2&gt;

&lt;p&gt;Many of these improvements were contributed by the greater GitLab community.
We look forward to your feedback and improvements on these great new features.
Together, we make an awesome team! 🏆&lt;&#x2F;p&gt;

&lt;p&gt;Let us know what you think in the comments below. What are you looking
forward to in this release? What can we continue to improve on?&lt;&#x2F;p&gt;

&lt;p&gt;Thanks for being a part of GitLab!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_2&#x2F;gitlab-11-2-released-cover.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.1 released with Security Dashboards and enhanced code search</title>
<release>11.1</release>
<link href='https://about.gitlab.com/releases/2018/07/22/gitlab-11-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/07/22/gitlab-11-1-released/</id>
<published>2018-07-22T00:00:00+00:00</published>
<author>
<name>Andreas Kämmerle</name>
</author>
<content type='html'>&lt;p&gt;In GitLab 11.1 we are shipping increased security visibility with dashboards and views to give you contextual information in the right place at the right time along with better code search, a heap of UX improvements, and a lot more!&lt;&#x2F;p&gt;

&lt;h2 id=&quot;increased-visibility-for-your-security-team&quot;&gt;Increased visibility for your security team&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab is designed for collaboration. Our mission is for everyone to contribute, and specifically we&#x27;ve designed a tool so that Product Management, Engineering, Quality Assurance, Operations, and Security can all collaborate together. It’s why we&#x27;ve built the entire software development and operations lifecycle into a single application. And it’s why we’ve built the Merge Request to be a powerful tool for collaboration.&lt;&#x2F;p&gt;

&lt;p&gt;But sometimes, the Merge Request isn’t the right view for your needs.&lt;&#x2F;p&gt;

&lt;p&gt;MRs are great when you want to see how a discrete change is affecting your app. But what if you want a higher-level view? Sometimes you want visibility into how all current security issues are affecting a branch in aggregate. The new &lt;a href=&quot;#security-dashboard-for-projects&quot;&gt;Security Dashboard&lt;&#x2F;a&gt; now gives you this visibility. This lets you make decisions about priority so you can focus remediation efforts on the most important vulnerabilities. Instead of having to collate reports across Merge Requests, now it’s all in one place. We see this as being especially helpful for security operations and engineering. They now have a specific view in GitLab to help them get their job done. Working right from the dashboard, security teams can adjust the criticality weight of vulnerabilities, creating issues to remediate critical items while dismissing others so they don’t repeatedly show up in reports.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;find-what-youre-looking-for-faster&quot;&gt;Find what you’re looking for faster&lt;&#x2F;h2&gt;

&lt;p&gt;Robust code searching capabilities are fundamental to developer productivity. Whether you are a new developer on a project or simply trying to navigate a large code base before adding a new feature, search is the way you become familiar with the key areas you need to understand. While code search has been available for a long time in GitLab, today, we&#x27;ve made it even better. With enhancements to the &lt;a href=&quot;#file-name-and-path-filters-for-advanced-code-search&quot;&gt;advanced search syntax&lt;&#x2F;a&gt;, you can now filter by filename, path, and extension, enabling you to find the right files more quickly.&lt;&#x2F;p&gt;

&lt;h2 id=&quot;even-more&quot;&gt;Even more!&lt;&#x2F;h2&gt;

&lt;p&gt;In addition to great new security functionality, we’ve also shipped an improved UX with a &lt;a href=&quot;#merge-request-widget-info-and-pipeline-sections-redesign&quot;&gt;redesigned Merge Request widget&lt;&#x2F;a&gt;, a &lt;a href=&quot;#view-merge-request-description-in-the-web-ide&quot;&gt;Merge Request panel in the Web IDE&lt;&#x2F;a&gt;, &lt;a href=&quot;#contribution-analytics-redesign&quot;&gt;redesigned contribution analytics&lt;&#x2F;a&gt;, and more!&lt;&#x2F;p&gt;

&lt;p&gt;Read on to see all features now available in GitLab 11.1.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_1&#x2F;gitlab-11-1-released-cover.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 11.0 released with Auto DevOps and License Management</title>
<release>11.0</release>
<link href='https://about.gitlab.com/releases/2018/06/22/gitlab-11-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/06/22/gitlab-11-0-released/</id>
<published>2018-06-22T00:00:00+00:00</published>
<author>
<name>Marcia Ramos</name>
</author>
<content type='html'>&lt;figure class=&quot;video_container&quot;&gt;
&lt;iframe src=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;embed&#x2F;EcFOx-FBrlQ&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;true&quot;&gt; &lt;&#x2F;iframe&gt;
&lt;&#x2F;figure&gt;

&lt;p&gt;Writing and delivering quality software poses many challenges.
First, you must solve tough business problems and craft great code.
But the challenges don&#x27;t stop there. You have to ensure your code
is fast, secure, and bug-free. You will need to build, integrate,
test, secure, review, configure, and deploy your code. Creating
and managing this pipeline is time consuming and complex.&lt;&#x2F;p&gt;

&lt;p&gt;Beyond making it easy to host and collaborate on public and private
repositories, GitLab also simplifies the rest of the process by
offering the whole delivery toolchain, built in. And now, it&#x27;s not
only built in, it&#x27;s automated. Simply commit your code and
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;topics&#x2F;autodevops&#x2F;&quot;&gt;&lt;strong&gt;Auto DevOps&lt;&#x2F;strong&gt;&lt;&#x2F;a&gt; can do the rest. Auto DevOps is a pre-built, fully
featured CI&#x2F;CD pipeline that automates the entire delivery process.
It is Generally Available and ready for prime time in GitLab 11.0.&lt;&#x2F;p&gt;

&lt;p&gt;Other key features we have released in GitLab 11.0 include
&lt;strong&gt;License Management&lt;&#x2F;strong&gt; to automatically detect licenses of
your project&#x27;s dependencies; enhanced &lt;strong&gt;Security Testing&lt;&#x2F;strong&gt;
of your code, containers, and dependencies; further &lt;strong&gt;Kubernetes&lt;&#x2F;strong&gt;
integration features; an enhanced &lt;strong&gt;Web IDE&lt;&#x2F;strong&gt;; enhanced
&lt;strong&gt;Epic and Roadmap&lt;&#x2F;strong&gt; views; &lt;strong&gt;Incremental Rollouts&lt;&#x2F;strong&gt;; and much more.&lt;&#x2F;p&gt;


&lt;p&gt;First, some more detail about these key features.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;#auto-devops-generally-available&quot;&gt;Auto DevOps&lt;&#x2F;a&gt; covers the end-to-end
lifecycle:&lt;&#x2F;strong&gt;
Simply commit your code to GitLab, then Auto DevOps does the rest:
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-build&quot;&gt;building&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-test&quot;&gt;testing&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-code-quality&quot;&gt;code quality scanning&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-sast&quot;&gt;security scanning&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-license-management&quot;&gt;license scanning&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-review-apps&quot;&gt;packaging&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-dast&quot;&gt;performance testing&lt;&#x2F;a&gt;,
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-deploy&quot;&gt;deploying&lt;&#x2F;a&gt;, and
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;#auto-monitoring&quot;&gt;monitoring&lt;&#x2F;a&gt;
your application.&lt;&#x2F;p&gt;

&lt;blockquote&gt;
  &lt;p&gt;“GitLab is a key part of our software-delivery processes and because
of them, we’ve improved our delivery velocity by four times and made
it immensely easier for our teams to collaborate,” said Chris Hill,
head of systems engineering for infotainment at Jaguar Land Rover.&lt;&#x2F;p&gt;

  &lt;p&gt;“We’re excited about Auto DevOps, because it will allow us to focus
on writing code and business value. GitLab can then handle the rest;
automatically building, testing, deploying, and even monitoring our
application.”&lt;&#x2F;p&gt;
&lt;&#x2F;blockquote&gt;

&lt;figure class=&quot;video_container&quot;&gt;
&lt;iframe src=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;embed&#x2F;0Tc0YYBxqi4&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;true&quot;&gt; &lt;&#x2F;iframe&gt;
&lt;&#x2F;figure&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;#license-management&quot;&gt;License Management&lt;&#x2F;a&gt; (software composition analysis):&lt;&#x2F;strong&gt;
Software is often a complex amalgamation of code that includes external components
(libraries, frameworks, and utilities). Each component typically includes
specific license permissions and limitations, so you need to track and manage
these dependencies for your application. GitLab 11.0 includes License Management
(software composition analysis) built into the Merge Request so you can track
and manage the included licenses.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;Security:&lt;&#x2F;strong&gt; This month we continue to improve GitLab&#x27;s built-in security
capabilities so you can &quot;shift security left&quot; and catch vulnerabilities early
via integrated Static and Dynamic Application Security Testing, along with
Dependency and Container Scanning. Specifically, we’ve extended coverage of
Static Analysis Security Testing (SAST) to
&lt;a href=&quot;#sast-for-net-and-scala&quot;&gt;include Scala and .Net&lt;&#x2F;a&gt;. We’re also including more
details in the SAST reports so you can get insight about specific issues
right there.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;Kubernetes:&lt;&#x2F;strong&gt; As part of our ongoing effort to improve the integration
with Kubernetes and make it easy for you to manage and monitor Kubernetes
from GitLab, there are several new features. Most notably, when you need
to debug or check on a pod, you can review the
&lt;a href=&quot;#view-kubernetes-pod-logs&quot;&gt;Kubernetes pod logs&lt;&#x2F;a&gt; directly from GitLab&#x27;s
deployment board.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;GitLab Web IDE:&lt;&#x2F;strong&gt; The more work you can do directly from the IDE, the
more productive you can be. Now, you are able to
&lt;a href=&quot;#cicd-pipeline-status-and-job-traces-in-the-web-ide&quot;&gt;view your CI&#x2F;CD pipelines from the IDE&lt;&#x2F;a&gt;
and get immediate feedback if a pipeline fails. Switching tasks
can be disruptive, so the updated Web IDE makes it easy to quickly switch
to the next merge request, to create, improve, or review without leaving
the Web IDE. This way, you can stay in the flow of writing and reviewing
code changes.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;strong&gt;Navigate Epics &#x2F; Roadmaps:&lt;&#x2F;strong&gt; When you want to visualize how
&lt;a href=&quot;#roadmap-date-ranges&quot;&gt;Epics and Roadmaps flow over time&lt;&#x2F;a&gt;, it can be helpful
to change the time scale and zoom out. We’ve updated the Epic&#x2F;Roadmap navigation
interface to make it easier to see the big picture and make planning easier.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;11_0&#x2F;gitlab-11-0-released-cover.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.8 released with incremental rollouts, plus open source push mirroring</title>
<release>10.8</release>
<link href='https://about.gitlab.com/releases/2018/05/22/gitlab-10-8-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/05/22/gitlab-10-8-released/</id>
<published>2018-05-22T00:00:00+00:00</published>
<author>
<name>Jeremy Watson</name>
</author>
<content type='html'>&lt;p&gt;We&#x27;re super excited to share a host of awesome additions now available in GitLab 10.8! We&#x27;ve improved release automation, sped up security vulnerability remediation, open sourced a highly requested paid feature, and plenty more.&lt;&#x2F;p&gt;


&lt;h3 class=&quot;intro-header&quot; id=&quot;deploy-with-confidence&quot;&gt;Deploy with confidence&lt;&#x2F;h3&gt;

&lt;p&gt;Releasing new features always comes with a bit of anxiety. Even with stringent pre-release testing, a change to your production codebase can result in unforeseen effects. Our new &lt;a href=&quot;#incremental-rollout-deployments&quot;&gt;Incremental Rollouts&lt;&#x2F;a&gt; feature helps developers deploy code with confidence by exposing changes to only a subset of users. Instead of rolling out to your entire user base all at once, incremental rollouts lets you gradually deploy to an increasing portion of your Kubernetes pods. If problems do occur, you can roll back without affecting the entire user base. We&#x27;re excited to provide an improved way to protect users and manage the unexpected, so you&#x27;re free to deploy more frequently.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header&quot; id=&quot;push-mirroring-is-now-open-source&quot;&gt;Push Mirroring is now open source&lt;&#x2F;h3&gt;

&lt;p&gt;When we &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;04&#x2F;22&#x2F;gitlab-8-7-released&#x2F;#remote-mirrors-ee-only&quot;&gt;first released Push Mirroring&lt;&#x2F;a&gt;, it was introduced as a paid feature. Since then, it has been one of the features that is &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;18732&quot;&gt;most requested&lt;&#x2F;a&gt; to be moved into our open source codebase. We take these requests seriously, and view having a balance between paid and open source features as &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;company&#x2F;stewardship&#x2F;&quot;&gt;good stewardship&lt;&#x2F;a&gt;. Today, we&#x27;re happy to share that &lt;a href=&quot;#push-mirroring-now-open-source&quot;&gt;Push Mirroring has been open sourced&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;This opens up a few key use cases for GitLab Core users including freelance development and migration. Freelance developers can now mirror each of their clients repos. While folks migrating to GitLab from other git-based repositories can now take advantage of push mirroring to ease the migration path.&lt;&#x2F;p&gt;

&lt;p&gt;Whenever possible, we like to open source features to not only encourage greater usage of GitLab, but also to encourage more folks to &lt;a href=&quot;&#x2F;community&#x2F;contribute&#x2F;&quot;&gt;contribute to open source software&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;ship-securely-faster&quot;&gt;Ship securely faster&lt;&#x2F;h3&gt;

&lt;p&gt;Keeping track of vulnerabilities without automation can be next to impossible. GitLab&#x27;s built-in security functionality includes   &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;sast&#x2F;&quot;&gt;SAST&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;dast&#x2F;&quot;&gt;DAST&lt;&#x2F;a&gt;, &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;container_scanning&#x2F;&quot;&gt;container scanning&lt;&#x2F;a&gt;, and &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;dependency_scanning&#x2F;&quot;&gt;dependency scanning&lt;&#x2F;a&gt; to keep you on top of vulnerabilities and ship secure code. And today, we&#x27;re improving the experience.&lt;&#x2F;p&gt;

&lt;p&gt;When a vulnerability appears in a report you&#x27;ll want to take action to either fix it or potentially ignore it if it&#x27;s a false positive. Now with &lt;a href=&quot;#interactive-feedback-in-security-reports-alpha&quot;&gt;Interactive Security Reports&lt;&#x2F;a&gt;, you&#x27;ll have the ability to take action right from the security report to either dismiss a vulnerability or create an issue to remediate it. By enabling users to take swifter action on vulnerabilities, we can help developers ship better, safer code.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;over-to-you&quot;&gt;Over to you!&lt;&#x2F;h3&gt;

&lt;p&gt;We couldn&#x27;t be more excited to get these changes to you and to hear your feedback. Let us know what you think in the comments below – what are you looking forward to in this release? What can we continue to improve on?&lt;&#x2F;p&gt;

&lt;p&gt;Thanks for being a part of GitLab ❤️&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_8&#x2F;10_8-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.7 released with open source Web IDE and SAST for Go and C&#x2F;C++!</title>
<release>10.7</release>
<link href='https://about.gitlab.com/releases/2018/04/22/gitlab-10-7-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/04/22/gitlab-10-7-released/</id>
<published>2018-04-22T00:00:00+00:00</published>
<author>
<name>Joshua Lambert</name>
</author>
<content type='html'>&lt;p&gt;Contributing features, reviewing changes, and deploying code is a day in the life of a developer.
Today we are making these tasks easier and more efficient with an amazing Web IDE, more flexible pipelines, additional security testing, and so much more.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;web-ide-is-now-open-source-and-generally-available&quot;&gt;Web IDE is now open source and generally available&lt;&#x2F;h2&gt;

&lt;p&gt;At GitLab, we want everyone to be able to contribute, whether you are working on your first commit and getting familiar with git, or an experienced developer reviewing a stack of changes. Setting up a local development environment, or needing to stash changes and switch branches locally, can add friction to the development process. Using the Web IDE you can change multiple files, preview Markdown, review the changes and commit directly all from a browser. You can even open the diff from a merge request and get a side by side view of the changes. The Web IDE
is generally available in 10.7 and &lt;a href=&quot;#web-ide-is-now-open-source&quot;&gt;is now open source&lt;&#x2F;a&gt;, so everyone can benefit.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;deploy-tokens&quot;&gt;Deploy Tokens&lt;&#x2F;h3&gt;

&lt;p&gt;For any organization working with &lt;a href=&quot;https:&#x2F;&#x2F;www.docker.com&#x2F;what-container&quot;&gt;containers&lt;&#x2F;a&gt;,
their registry is a key component in their infrastructure. It serves as a versioned
repository, providing an easy and secure way of interacting with
your container images. A common use for the registry is to serve images to an orchestrator
like &lt;a href=&quot;https:&#x2F;&#x2F;kubernetes.io&#x2F;&quot;&gt;Kubernetes&lt;&#x2F;a&gt;. It&#x27;s important for Kubernetes to have access on an ongoing basis.
For example, Kubernetes will pull an image on initial deployment, any time a pod restarts, or when scaling additional pods.&lt;&#x2F;p&gt;

&lt;p&gt;Previously there were two ways to grant access to the registry and repository. One way is the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;new_ci_build_permissions_model.html#job-token&quot;&gt;CI job token&lt;&#x2F;a&gt; which provides temporary access for length of the job, after which it expires. &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;profile&#x2F;personal_access_tokens.html&quot;&gt;Personal Access Tokens&lt;&#x2F;a&gt; provide long term access but are tied to a specific user. When using the CI Job Token, Kubernetes loses access once the CI job has completed, so ongoing events like pod restarts and scaling fail. Using Personal Access Tokens is also undesirable, because access has to be either shared with a user, or a separate service account must be created which takes up a license.&lt;&#x2F;p&gt;

&lt;p&gt;To address these needs more cleanly we have added &lt;a href=&quot;#deploy-tokens&quot;&gt;Deploy Tokens&lt;&#x2F;a&gt;, providing long lived read-only authentication. With a Deploy Token, Kubernetes can now get the images it needs, when it needs them, without being associated with a particular user or having unnecessary access rights.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;cicd-flow-control-based-on-variables&quot;&gt;CI&#x2F;CD flow control based on variables&lt;&#x2F;h3&gt;

&lt;p&gt;A company&#x27;s CI&#x2F;CD service is the engine of their software engineering process,
performing a wide variety of roles from building and testing software, deploying
it to production, and frequently more creative tasks as well. With such a varied
and open-ended set of uses, it is important for users to be able to run specific
jobs only when they need to. GitLab CI&#x2F;CD already provides a rich set of options
for &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;jobs&#x2F;job_control.html#specify-when-jobs-run-with-only-and-except&quot;&gt;managing flow control&lt;&#x2F;a&gt;,
but there were some use cases like a nightly build that were not easy to address. In 10.7 jobs can now be
started based on the &lt;a href=&quot;#variables-support-in-only-and-except-keywords&quot;&gt;value of specific variables&lt;&#x2F;a&gt;, enabling new use cases like jobs specific to particular a
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;pipelines&#x2F;schedules.html&quot;&gt;pipeline schedule&lt;&#x2F;a&gt; or &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;triggers&#x2F;#making-use-of-trigger-variables&quot;&gt;API trigger&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;sast-for-go-and-cc-languages&quot;&gt;SAST for Go and C&#x2F;C++ languages&lt;&#x2F;h3&gt;

&lt;p&gt;As part of &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-raises-20-million-to-complete-devops&#x2F;&quot;&gt;Complete DevOps&lt;&#x2F;a&gt;, we are providing a great set of security tools out of the box. &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;application_security&#x2F;sast&#x2F;&quot;&gt;Static Application Security Testing (SAST)&lt;&#x2F;a&gt; analyzes your source code for known vulnerabilities, and outputs the results directly on the merge request for easy review. In order to analyze your code however, SAST needs to have support for your language. For this reason we have been broadening the scope of SAST, and now &lt;a href=&quot;#sast-for-go-and-cc&quot;&gt;support Go and C&#x2F;C++&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_7&#x2F;10_7-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.6 released with CI&#x2F;CD for GitHub and deeper Kubernetes integration</title>
<release>10.6</release>
<link href='https://about.gitlab.com/releases/2018/03/22/gitlab-10-6-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/03/22/gitlab-10-6-released/</id>
<published>2018-03-22T00:00:00+00:00</published>
<author>
<name>Victor Wu</name>
</author>
<content type='html'>&lt;p&gt;Continuous integration, continuous delivery, and continuous deployment form the backbone of modern DevOps. GitLab features built-in CI&#x2F;CD that has received a lot of positive attention from &lt;a href=&quot;http:&#x2F;&#x2F;blog.thehumangeo.com&#x2F;gitlab-autoscale-runners.html&quot;&gt;developers&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;blog&#x2F;continuous-integration-ticketmaster&#x2F;&quot;&gt;enterprises&lt;&#x2F;a&gt;, and &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-leader-continuous-integration-forrester-wave&#x2F;&quot;&gt;analysts&lt;&#x2F;a&gt; alike.&lt;&#x2F;p&gt;

&lt;p&gt;But one thing that was missing was that you couldn&#x27;t use GitLab CI&#x2F;CD with GitHub.  Well today, we’ve fixed that.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;introducing-gitlab-cicd-for-github&quot;&gt;Introducing GitLab CI&#x2F;CD for GitHub&lt;&#x2F;h2&gt;

&lt;p&gt;While GitLab works best when you use it &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;product&#x2F;single-application&#x2F;&quot;&gt;all end-to-end&lt;&#x2F;a&gt;, we also seek to &lt;a href=&quot;&#x2F;direction&#x2F;#plays-well-with-others&quot;&gt;play well with others&lt;&#x2F;a&gt;. In this spirit, we’ve added &lt;a href=&quot;&#x2F;solutions&#x2F;github&#x2F;&quot;&gt;CI&#x2F;CD integration with GitHub&lt;&#x2F;a&gt;, and more generally the ability
to &lt;a href=&quot;#gitlab-cicd-for-external-repos&quot;&gt;integrate CI&#x2F;CD with other external repos&lt;&#x2F;a&gt; like Bitbucket as well. We see four primary audiences that this functionality is designed for. &lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;open-source-projects&quot;&gt;Open source projects&lt;&#x2F;h3&gt;

&lt;p&gt;If you have a public, open source project on GitHub you can now take advantage of free CI&#x2F;CD on GitLab.com. As part of our commitment to open source, we offer all public projects our highest tier features (Gold) for free. While other CI&#x2F;CD vendors limit you to running a handful of concurrent jobs, &lt;a href=&quot;https:&#x2F;&#x2F;GitLab.com&quot;&gt;GitLab.com&lt;&#x2F;a&gt; gives open source projects hundreds of concurrent jobs with 50,000 free CI pipeline minutes per month.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;large-enterprises&quot;&gt;Large Enterprises&lt;&#x2F;h3&gt;

&lt;p&gt;When we talk to our largest customers they tell us that they often have many teams using many different tools. They want to standardize on GitLab for CI&#x2F;CD but code is stored in GitLab, GitHub, and other repos. This feature now allows enterprises to use common CI&#x2F;CD pipelines across all of their different repos. This is a key audience and why we’ve made CI&#x2F;CD for GitHub part of our self-managed Premium plan.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;anyone-using-githubcom&quot;&gt;Anyone using GitHub.com&lt;&#x2F;h3&gt;

&lt;p&gt;While GitLab is designed to use SCM &amp;amp; CI&#x2F;CD in the same application, we understand the appeal of using GitLab CI&#x2F;CD with GitHub version control. So, for the next year we are making the GitLab CI&#x2F;CD for GitHub feature a part of our &lt;a href=&quot;https:&#x2F;&#x2F;GitLab.com&quot;&gt;GitLab.com&lt;&#x2F;a&gt; Free tier. That means anyone using GitHub from personal projects and startups to SMBs can use GitLab CI&#x2F;CD for free. Starting at 2000 free CI pipeline minutes per month, folks can also &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;runners&#x2F;runners_scope.html#specific-runners&quot;&gt;add their own Runners&lt;&#x2F;a&gt; or upgrade plans to get more.&lt;&#x2F;p&gt;

&lt;h3 class=&quot;intro-header-h3&quot; id=&quot;gemnasium-customers&quot;&gt;Gemnasium customers&lt;&#x2F;h3&gt;

&lt;p&gt;We recently &lt;a href=&quot;&#x2F;press&#x2F;releases&#x2F;2018-01-30-gemnasium-acquisition&#x2F;&quot;&gt;acquired Gemnasium&lt;&#x2F;a&gt;. While we are super excited about having such a great team join our ranks, we also want to take care of folks that were using Gemnasium and provide them a migration path. We’ve already &lt;a href=&quot;&#x2F;releases&#x2F;2018&#x2F;02&#x2F;22&#x2F;gitlab-10-5-released&#x2F;#gemnasium-dependency-checks&quot;&gt;shipped Gemnasium features&lt;&#x2F;a&gt; as part of our built-in security scanning. Now, GitLab CI&#x2F;CD for GitHub allows Gemnasium customers that were using GitHub + Gemnasium to begin using GitLab CI&#x2F;CD for their security needs without needing to migrate their code.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;kubernetes-on-gitlab-keeps-getting-better&quot;&gt;Kubernetes on GitLab keeps getting better&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab continues to invest in integrating with containerization. In 10.4 we release &lt;a href=&quot;&#x2F;releases&#x2F;2018&#x2F;01&#x2F;22&#x2F;gitlab-10-4-released&#x2F;#gitlab-clusters-now-generally-available&quot;&gt;Kubernetes Cluster Integration and GKE Integration to General Availability&lt;&#x2F;a&gt;. With this release, we make it even easier for users to use Kubernetes with GitLab. You can now &lt;a href=&quot;#quick-deploy-of-gitlab-runner-to-kubernetes-cluster&quot;&gt;deploy a GitLab Runner to your connected Kubernetes cluster with a single click&lt;&#x2F;a&gt;. You can also &lt;a href=&quot;#kubernetes-cluster-monitoring&quot;&gt;monitor your connected Kubernetes cluster from within GitLab&lt;&#x2F;a&gt; itself. And you can now also &lt;a href=&quot;#ingress-ip-address-on-kubernetes-cluster-page&quot;&gt;see the IP address of an Ingress controller connected to your Kubernetes cluster&lt;&#x2F;a&gt;, again, right inside GitLab!&lt;&#x2F;p&gt;

&lt;style&gt;
@media (min-width: 768px) {
  .intro-header-h3 {
    font-size: 28px !important;
  }
}
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_6&#x2F;10_6-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.5 released with Let&#x27;s Encrypt integration, Gemnasium dependency checks, and CI&#x2F;CD external files</title>
<release>10.5</release>
<link href='https://about.gitlab.com/releases/2018/02/22/gitlab-10-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/02/22/gitlab-10-5-released/</id>
<published>2018-02-22T00:00:00+00:00</published>
<author>
<name>Fabio Busatto</name>
</author>
<content type='html'>&lt;p&gt;In this month’s release of GitLab 10.5 we’ve added capabilities to encrypt GitLab traffic easily, improve application security, scaling CI&#x2F;CD management, and so much more.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;secure-gitlab-deployments-in-less-time&quot;&gt;Secure GitLab deployments in less time&lt;&#x2F;h2&gt;

&lt;p&gt;HTTPS is a pillar of internet security and a must-have if your GitLab instance is exposed to the public internet. It provides two key benefits. First, traffic is encrypted to and from the server, protecting credentials and other sensitive data from potential eavesdropping. Second, it allows users to verify the site identity. Without a verified identity it&#x27;s possible for users to log into the wrong site. These capabilities are particularly important for mobile and remote users, who often use public unsecured Wi-Fi increasing the risk of snooping or interacting with a malicious site.&lt;&#x2F;p&gt;

&lt;p&gt;Although HTTPS provides great security, setting up HTTPS and requesting certificates can be a hassle involving credit cards and key management.&lt;&#x2F;p&gt;

&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;letsencrypt.org&#x2F;&quot;&gt;Let’s Encrypt&lt;&#x2F;a&gt; is a free, automated, and open certificate authority. With GitLab 10.5 we’ve added &lt;a href=&quot;#instant-ssl-with-lets-encrypt-for-gitlab&quot;&gt;Let’s Encrypt integration&lt;&#x2F;a&gt;, allowing you to enable instant SSL certificates with a single option. Enabling Let’s Encrypt on your GitLab instance ensures traffic to your GitLab instance is encrypted and the identity of your site is verified. The Let’s Encrypt integration is available on both paid and open source GitLab.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;scale-your-pipeline-management&quot;&gt;Scale your pipeline management&lt;&#x2F;h2&gt;

&lt;p&gt;Today, we’re releasing a simple feature with powerful implications.&lt;&#x2F;p&gt;

&lt;p&gt;Running DevOps in an enterprise environment comes with some unique challenges. For many of our largest customers, the DevOps team is responsible for providing CI&#x2F;CD pipelines to a large number of development teams throughout the organization. Previously, this was a painful process to manage. There wasn’t a scalable way to distribute reusable pipeline configuration which meant code needed to be manually copied between multiple &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; files in multiple projects. This was a labor-intensive and error-prone process. Additionally, it didn&#x27;t provide adequate controls to ensure testing and deployment is consistently enforced for each repo.&lt;&#x2F;p&gt;

&lt;p&gt;Starting with 10.5, you can now &lt;a href=&quot;#include-external-files-in-cicd-pipeline-definition&quot;&gt;include external files in CI&#x2F;CD pipeline definition&lt;&#x2F;a&gt;. Included files can be either local (contained in the same repo) or remote (accessible via HTTP&#x2F;HTTPS).  Including local files allows a large and complex &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; to be broken up in to modular chunks that are easier to maintain. Remote files allow these modular chunks to be distributed across thousands (or potentially millions) of repositories. Now there’s a simple, consistent, and maintainable way to distribute pipeline configuration.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;better-security-testing-with-gemnasium&quot;&gt;Better security testing with Gemnasium&lt;&#x2F;h2&gt;

&lt;p&gt;Less than a month ago, &lt;a href=&quot;&#x2F;press&#x2F;releases&#x2F;2018-01-30-gemnasium-acquisition&#x2F;&quot;&gt;GitLab acquired Gemnasium&lt;&#x2F;a&gt;. As promised, we haven’t wasted any time in bringing Gemnasium’s advanced dependency-checking functionality to GitLab users. Often, when companies make acquisitions, they tend to create bolt-on additions or package functionality as separate offerings. GitLab’s vision is to provide a &lt;a href=&quot;&#x2F;direction&#x2F;#single-application&quot;&gt;single application architecture&lt;&#x2F;a&gt; so that dev, QA, security, and ops can work concurrently off the same data in the same interface. In this spirit we’ve &lt;a href=&quot;#gemnasium-dependency-checks&quot;&gt;integrated Gemnasium’s technology&lt;&#x2F;a&gt; seamlessly into GitLab CI&#x2F;CD, supercharging security testing.&lt;&#x2F;p&gt;

&lt;p&gt;Thanks to advanced algorithms and a larger vulnerability database, GitLab now provides more complete results in JavaScript, Ruby, and Python. We’ve also added PHP and Java support so you have five languages total.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;see-all-the-features&quot;&gt;See all the features&lt;&#x2F;h2&gt;

&lt;p&gt;This post highlights 26 enhancements (18 of which are available in open source GitLab!) For the full list of improvements see the &lt;a href=&quot;#changelog&quot;&gt;changelog&lt;&#x2F;a&gt;. Or read on to learn more about all of the key features shipped in 10.5!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_5&#x2F;10_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.4 released with Dynamic Application Security Testing and Web IDE (beta)</title>
<release>10.4</release>
<link href='https://about.gitlab.com/releases/2018/01/22/gitlab-10-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2018/01/22/gitlab-10-4-released/</id>
<published>2018-01-22T00:00:00+00:00</published>
<author>
<name>James Ramsay</name>
</author>
<content type='html'>&lt;p&gt;In this month&#x27;s release of GitLab 10.4 – the first of 2018 – we&#x27;ve added
capabilities to improve planning, testing, merge requests, and deployment. This
release also includes new security testing capabilities and the first iteration of
our Web IDE, part of our ambitious product vision for
&lt;a href=&quot;&#x2F;blog&#x2F;from-dev-to-devops&#x2F;&quot;&gt;Complete DevOps&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;security-testing&quot;&gt;Security testing&lt;&#x2F;h2&gt;

&lt;p&gt;As part of Complete Devops, we want to offer powerful security tools out of the
box. We recently released static application security testing and are now
expanding that with
&lt;a href=&quot;#dynamic-application-security-testing-dast&quot;&gt;Dynamic Application Security Testing (DAST)&lt;&#x2F;a&gt;
and
&lt;a href=&quot;#sast-for-docker-containers&quot;&gt;Static Application Security Testing (SAST) for Docker Containers&lt;&#x2F;a&gt;.
DAST, SAST for Docker Containers, and Browser Performance Testing have also
been added as a best practice to Auto DevOps.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;faster-editing&quot;&gt;Faster editing&lt;&#x2F;h2&gt;

&lt;p&gt;&quot;If you can do it in less than two minutes, do it now&quot; states the two-minute
rule of &lt;a href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Getting_Things_Done&quot;&gt;Getting Things Done&lt;&#x2F;a&gt;.
Writing a small fix or correcting a typo should be fast, but this is rarely the
case when we need to stash changes and switch to a different context.&lt;&#x2F;p&gt;

&lt;p&gt;Delaying a fix or waiting to address feedback on a merge request increases
cycle time, and it&#x27;s even worse for distributed teams where hours quickly become days,
all for avoiding a &lt;code&gt;git stash&lt;&#x2F;code&gt;. The &lt;a href=&quot;#web-ide-editor-beta&quot;&gt;new editor&lt;&#x2F;a&gt;, which is
the first release of the GitLab Web IDE,
makes it easier to contribute changes like these from the GitLab interface.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;see-all-the-features&quot;&gt;See all the features&lt;&#x2F;h2&gt;

&lt;p&gt;We&#x27;ve also shipped many exciting improvements this month to Epics, Merge
Requests, Geo, Runner, Git LFS, SSH, Monitoring, and Auto DevOps.&lt;&#x2F;p&gt;

&lt;p&gt;Read on to learn more about all of the key features shipped in 10.4!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_4&#x2F;10_4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.3 released with Static Application Security Testing and Browser Performance Testing</title>
<release>10.3</release>
<link href='https://about.gitlab.com/releases/2017/12/22/gitlab-10-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/12/22/gitlab-10-3-released/</id>
<published>2017-12-22T00:00:00+00:00</published>
<author>
<name>Mark Pundsack</name>
</author>
<content type='html'>&lt;p&gt;In this month’s release of GitLab 10.3 we’ve added new ways to ensure that your
code changes are both secure and fast, enhanced your planning and collaboration
workflow, and improved your ability to build and ship.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;security-and-testing&quot;&gt;Security and testing&lt;&#x2F;h2&gt;

&lt;p&gt;Not too long ago, we announced our ambitious &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-raises-20-million-to-complete-devops&#x2F;&quot;&gt;vision for Complete
DevOps&lt;&#x2F;a&gt; and with
GitLab 10.3 we&#x27;re adding several exciting new features that help bring that
vision to life. &lt;a href=&quot;#static-application-security-testing-sast&quot;&gt;Static Application Security
Testing&lt;&#x2F;a&gt; and &lt;a href=&quot;#browser-performance-testing&quot;&gt;Browser Performance
Testing&lt;&#x2F;a&gt; expand the scope of your CI&#x2F;CD pipeline
with security and performance checks, respectively. SAST
has already been added as a best practice to Auto DevOps, with Browser
Performance Testing soon to follow.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;discussion-and-collaboration&quot;&gt;Discussion and collaboration&lt;&#x2F;h2&gt;

&lt;p&gt;In 10.3, we also include &lt;a href=&quot;#merge-request-commit-discussions&quot;&gt;Merge Request Commit Discussions&lt;&#x2F;a&gt; to allow you to start a
conversation on specifics commits within a merge request.&lt;&#x2F;p&gt;

&lt;p&gt;Thanks to our &lt;a href=&quot;#mvp&quot;&gt;MVP&lt;&#x2F;a&gt;, you can now
&lt;a href=&quot;#customize-branch-name-when-creating-merge-request-from-issue&quot;&gt;customize the branch name when you start a merge request from an issue&lt;&#x2F;a&gt;. This
improvement is important to allow you to rapidly start MRs directly from
issues without having to break your branching strategy.&lt;&#x2F;p&gt;

&lt;p&gt;Sometimes an image is worth a million words. With GitLab 10.3, we added
support for &lt;a href=&quot;#flow-charts-sequence-diagrams-and-gantt-diagrams-in-gitlab-flavored-markdown-gfm-with-mermaid&quot;&gt;flow charts, sequence diagrams, and Gantt diagrams in GitLab Flavored Markdown (GFM) with Mermaid&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;build-and-ship&quot;&gt;Build and ship&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab 10.3 adds support for &lt;a href=&quot;#multiple-kubernetes-clusters-per-project-beta&quot;&gt;multiple Kubernetes clusters per
project&lt;&#x2F;a&gt;, which enables a common
best practice of keeping your production cluster isolated from your dev and test
cluster(s).&lt;&#x2F;p&gt;

&lt;p&gt;With 10.3 we&#x27;re shipping an enhancement to Auto DevOps. Now, when you enable
Auto DevOps for your project, the &lt;a href=&quot;#automatically-run-first-pipeline-when-enabling-auto-devops&quot;&gt;first pipeline will run automatically&lt;&#x2F;a&gt;,
without needing to trigger it manually.&lt;&#x2F;p&gt;

&lt;p&gt;Artifacts can expire or be manually deleted so we&#x27;re introducing &lt;a href=&quot;#strict-check-on-artifacts-dependencies&quot;&gt;strict checking on artifact dependencies&lt;&#x2F;a&gt;, so that jobs
will fail if their dependencies cannot be found.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;see-all-the-features&quot;&gt;See all the features&lt;&#x2F;h2&gt;

&lt;p&gt;We&#x27;re also shipping improvements to Merge Requests, Epics, Milestones,
Repository Mirroring, API, Geo, Runner, Protected Branches, Quick Actions, and
Issue Boards.&lt;&#x2F;p&gt;

&lt;p&gt;Read on to see everything that was released in GitLab 10.3!&lt;&#x2F;p&gt;

&lt;p&gt;We thank you for helping us to create great software with GitLab in 2017! We wish
you a Merry Christmas, happy holidays, and a new year full of great surprises!
Cheers!&lt;&#x2F;p&gt;

&lt;style type=&quot;text&#x2F;css&quot;&gt;
  .intro-header {
    font-size: 33px !important;
  }
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_3&#x2F;10_3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.2 released with Configurable Issue Boards and GitLab Geo General Availability</title>
<release>10.2</release>
<link href='https://about.gitlab.com/releases/2017/11/22/gitlab-10-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/11/22/gitlab-10-2-released/</id>
<published>2017-11-22T00:00:00+00:00</published>
<author>
<name>Joshua Lambert</name>
</author>
<content type='html'>&lt;p&gt;In this month’s release of GitLab 10.2 we’ve added capabilities to improve
planning, reliability, deployment, and so much more.&lt;&#x2F;p&gt;


&lt;h2 class=&quot;intro-header&quot; id=&quot;plan-your-work-more-efficiently&quot;&gt;Plan your work more efficiently&lt;&#x2F;h2&gt;

&lt;p&gt;If you’re like me, GitLab issues are water. Essential for life, but huge
volumes make you drown.&lt;&#x2F;p&gt;

&lt;p&gt;Getting a view of only the issues you care about for a particular context
is crucial to being effective, especially in shared views with teams.
Previously, GitLab let you use filters to
show a set of issues tied to a particular milestone or label in an issue board,
but that was only temporary. Your workflow may have depended on bookmarking a board
URL and sharing it with team members as a workaround.&lt;&#x2F;p&gt;

&lt;p&gt;Today, with &lt;a href=&quot;#configurable-issue-boards&quot;&gt;Configurable Issue Boards&lt;&#x2F;a&gt; you can
now save the scope itself (milestone, labels, assignee
and weight) to a board, ensuring that every team member sees exactly the same issues.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;fetch-faster&quot;&gt;Fetch faster&lt;&#x2F;h2&gt;

&lt;p&gt;Teams are increasingly distributed across larger geographical areas. This is
one reason why Git is so popular, Git is distributed by nature – your local
Git repository has a copy of every commit, file, and branch in the history of
the project. Once the history is downloaded, development is fast!&lt;&#x2F;p&gt;

&lt;p&gt;But if you only have one physical instance, it may be located far away from your distributed teams. The latency caused by this distance can significantly slow fetch operations when large quantities of small files are
being downloaded. Today, we&#x27;re excited to share that &lt;a href=&quot;#gitlab-geo-is-now-generally-available&quot;&gt;GitLab Geo has been released into General Availability&lt;&#x2F;a&gt;. GitLab Geo allows you to run read-only replicas of GitLab, including the GitLab
interface, close to your distributed teams.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;stay-up-and-running-at-scale&quot;&gt;Stay up and running at scale&lt;&#x2F;h2&gt;

&lt;p&gt;GitLab’s single application architecture gives you one unified
data store across your issue tracking, source code repository, CI&#x2F;CD,
and monitoring. This unified approach enables additional insights, a better user experience, and greater efficiencies throughout your development organization.&lt;&#x2F;p&gt;

&lt;p&gt;With GitLab at the core of many software engineering groups, it&#x27;s important however to ensure it is running at peak performance, no matter the time of day. Today we’re proud to announce that &lt;a href=&quot;#postgres-ha-is-now-generally-available&quot;&gt;PostgreSQL High Availability is now Generally Available&lt;&#x2F;a&gt;, making it easy to set up and run a Postgres cluster for GitLab.
With a simple Omnibus-based installation and automatic failover, your developers can work without disruption.&lt;&#x2F;p&gt;

&lt;div class=&quot;panel panel-gitlab-purple&quot;&gt;
  &lt;p class=&quot;panel-heading&quot;&gt;In a nutshell:&lt;&#x2F;p&gt;
  &lt;div class=&quot;panel-body&quot;&gt;
    &lt;ul&gt;
      &lt;li&gt;Single Source of Truth == 😃&lt;&#x2F;li&gt;
      &lt;li&gt;Single Point of Failure == 😱&lt;&#x2F;li&gt;
    &lt;&#x2F;ul&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;div&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;deploy-on-kubernetes-even-faster&quot;&gt;Deploy on Kubernetes even faster&lt;&#x2F;h2&gt;

&lt;p&gt;With each release, we are making the GitLab Kubernetes experience even better.
Last month, we made it easy to spin up new Kubernetes clusters with a few clicks.
But once you have a new cluster ready, you need to set up additional services
such as an external access controller. In this month’s release,
we’re removing that time sink from your schedule by adding &lt;a href=&quot;#easy-deployment-of-helm-and-ingress-on-kubernetes&quot;&gt;one-click installs for Tiller and Ingress&lt;&#x2F;a&gt;. Be on the lookout
next month for multi-cluster deployments. We aim to make each iterative step a
value-packed ship in and of itself.&lt;&#x2F;p&gt;

&lt;h2 class=&quot;intro-header&quot; id=&quot;see-all-the-features&quot;&gt;See all the features&lt;&#x2F;h2&gt;

&lt;p&gt;We’ve shipped a lot of exciting features this month including
&lt;a href=&quot;#commit-author-restriction&quot;&gt;Commit Author Restriction&lt;&#x2F;a&gt; and
&lt;a href=&quot;#promote-project-milestones-to-group-milestones&quot;&gt;Promote Project Milestones to Group Milestones&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;Read on to learn more about all of the key features shipped in 10.2!&lt;&#x2F;p&gt;

&lt;style type=&quot;text&#x2F;css&quot;&gt;
  .intro-header {
    font-size: 33px !important;
  }
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_2&#x2F;10_2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.1 released with Image Discussions and Rejection of Unsigned Commits</title>
<release>10.1</release>
<link href='https://about.gitlab.com/releases/2017/10/22/gitlab-10-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/10/22/gitlab-10-1-released/</id>
<published>2017-10-22T00:00:00+00:00</published>
<author>
<name>Achilleas Pipinellis</name>
</author>
<content type='html'>&lt;p&gt;Καλημέρα! (Good morning!) This month we&#x27;re coming to you live from GitLab all
hands in Heraklion, Greece, to release GitLab 10.1. 🚀&lt;&#x2F;p&gt;

&lt;p&gt;Since GitLab&#x27;s inception, we envisioned a world where
&lt;a href=&quot;&#x2F;direction&#x2F;#vision&quot;&gt;everyone can contribute&lt;&#x2F;a&gt;, and with each release we&#x27;re one
step closer. With GitLab 10.1, we bring more tools for better collaboration,
enhanced security and authentication, as well as improved performance and UX.&lt;&#x2F;p&gt;


&lt;p&gt;For far too long a group of folks have been left out of the discussion and we
think it&#x27;s time that got fixed. With GitLab 10.1 we&#x27;re changing how you should
think about version control and discussion.
Commenting on lines of code works great when the discussion centers around text,
but what about images? After all, if the code being written has an app UI, web
page, or generates a printed asset then it makes sense that you&#x27;d want to be
able to talk about text and images in the same way. With
&lt;a href=&quot;#image-discussions&quot;&gt;Image Discussions&lt;&#x2F;a&gt; we&#x27;re opening up a whole new way to
collaborate. Extending on collaboration, you can now
&lt;a href=&quot;#merge-requests-across-forks&quot;&gt;create merge requests across forks&lt;&#x2F;a&gt; of a
canonical repository.&lt;&#x2F;p&gt;

&lt;p&gt;Being able to work under a secure environment is very important, and with each
release we are constantly improving the security and authentication mechanisms.
This time, we have added &lt;a href=&quot;#ldap-group-sync-filters&quot;&gt;LDAP group sync filters&lt;&#x2F;a&gt;,
as well as the ability to &lt;a href=&quot;#reject-unsigned-commits&quot;&gt;reject unsigned commits&lt;&#x2F;a&gt;.
The &lt;a href=&quot;#improved-admin-audit-log&quot;&gt;admin audit log&lt;&#x2F;a&gt; has been improved to also
include more metrics and &lt;a href=&quot;#signing-commits-with-gpg-subkeys&quot;&gt;GPG subkeys support&lt;&#x2F;a&gt; has
been added.&lt;&#x2F;p&gt;

&lt;p&gt;An open source project can attract a lot of visitors and contributors. Although
one would expect civilized discussions to take place, that&#x27;s not always
the case. With GitLab 10.1, a moderation tool is in place and you are able to
&lt;a href=&quot;#lock-discussions&quot;&gt;lock discussions on issues and merge requests&lt;&#x2F;a&gt;
to avoid unnecessary friction among your community.&lt;&#x2F;p&gt;

&lt;p&gt;Going strong with our &lt;a href=&quot;&#x2F;blog&#x2F;from-dev-to-devops&#x2F;&quot;&gt;DevOps vision&lt;&#x2F;a&gt;, we&#x27;ve
made it really easy to &lt;a href=&quot;#easy-creation-of-kubernetes-clusters-on-google-container-engine-(beta)&quot;&gt;create clusters on Google Kubernetes Engine from within
GitLab&lt;&#x2F;a&gt;.
The &lt;a href=&quot;#online-view-of-html-artifacts&quot;&gt;online view of HTML artifacts&lt;&#x2F;a&gt;
is also another great addition that will make it even easier to view your test
reports right from your web browser.&lt;&#x2F;p&gt;

&lt;p&gt;Dedicated to our open source stewardship, the
&lt;a href=&quot;#semi-linear-history-and-fast-forward-merge-requests-in-ce&quot;&gt;fast-forward option in merge requests&lt;&#x2F;a&gt;
previously on Enterprise Edition Starter is now brought to Community Edition.&lt;&#x2F;p&gt;

&lt;p&gt;In the UX side of things, GitLab now comes with an &lt;a href=&quot;#improved-new-project-page&quot;&gt;improved new project page&lt;&#x2F;a&gt;
so that it&#x27;s easier to decide the kind of project you want to create. Whether
you want to start from scratch, use a template or import from another provider,
you can now achieve it easier than before.&lt;&#x2F;p&gt;

&lt;p&gt;We&#x27;re dedicated to making GitLab perform better and faster under heavy load,
and GitLab 10.1 is no exception. This release comes with many
&lt;a href=&quot;#performance-improvements&quot;&gt;performance improvements&lt;&#x2F;a&gt; including faster viewing
of merge requests and general initial page load improvements.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_1&#x2F;10_1-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 10.0 released with Auto DevOps and Group Issue Boards</title>
<release>10.0</release>
<link href='https://about.gitlab.com/releases/2017/09/22/gitlab-10-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/09/22/gitlab-10-0-released/</id>
<published>2017-09-22T00:00:00+00:00</published>
<author>
<name>Mike Bartlett</name>
</author>
<content type='html'>&lt;p&gt;From the formulation of an idea to executing and monitoring it in production, DevOps establishes
a culture and environment where developing, testing, and releasing software can happen quickly, frequently,
and more reliably.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab 10.0 delivers a hands-free
DevOps environment with the introduction of &lt;a href=&quot;#auto-devops&quot;&gt;Auto DevOps&lt;&#x2F;a&gt;, allowing your team to easily configure and adopt
modern development practices in your workflow. Not only that, there&#x27;s &lt;a href=&quot;#new-user-experience&quot;&gt;new navigation&lt;&#x2F;a&gt; and a new way of &lt;a href=&quot;#group-issue-boards&quot;&gt;collaborating across groups&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;


&lt;p&gt;With every monthly release of GitLab, we introduce new capabilities and improve our existing features. GitLab 10.0 is no exception and includes numerous new additions, such as the ability to &lt;a href=&quot;#automatically-resolve-outdated-mr-discussions&quot;&gt;automatically resolve outdated merge request discussions&lt;&#x2F;a&gt;, improvements to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;group&#x2F;subgroups&#x2F;index.html&quot;&gt;subgroups&lt;&#x2F;a&gt;, and an &lt;a href=&quot;#api-support-for-wikis&quot;&gt;API for Wiki&lt;&#x2F;a&gt; thanks to a contribution from our open source community.&lt;&#x2F;p&gt;

&lt;p&gt;GitLab&#x27;s powerful issue management capabilities keep getting better with every release. Filtering and searching issues across groups has been &lt;a href=&quot;#group-merge-requests-search-and-filter-bar&quot;&gt;vastly improved&lt;&#x2F;a&gt;, our updated UX makes moving issues &lt;a href=&quot;#move-issues-from-the-sidebar&quot;&gt;easier to discover&lt;&#x2F;a&gt; and can be automated &lt;a href=&quot;#move-issue-quick-action&quot;&gt;through quick action commands&lt;&#x2F;a&gt;. GitLab Enterprise Edition Premium customers using JIRA can now &lt;a href=&quot;#access-gitlab-commits-and-branches-in-jira-development-panel&quot;&gt;see commits and branches&lt;&#x2F;a&gt; in JIRA&#x27;s development panel.&lt;&#x2F;p&gt;

&lt;p&gt;Security and performance continues to improve. Administrators can now &lt;a href=&quot;#ssh-key-length-restrictions&quot;&gt;restrict SSH&lt;&#x2F;a&gt; access through technology and key length. LDAP Group Sync can &lt;a href=&quot;#ldap-group-sync-api&quot;&gt;be automated&lt;&#x2F;a&gt; through our API and can now lock down &lt;a href=&quot;#ldap-group-sync-improvements-for-external-users&quot;&gt;External Users&lt;&#x2F;a&gt; at point of login as well. &lt;a href=&quot;#performance-improvements&quot;&gt;Performance&lt;&#x2F;a&gt; continues to get faster, improving page loading speeds, the speed of creating projects and performing commits, and reduced memory usage.&lt;&#x2F;p&gt;

&lt;style&gt;
  .blog.article .author,
  .blog.article .author a,
  .blog.article .date,
  .blog.article .date a,
  .blog.article .author-twitter i,
  .blog.article .author-gitlab i {
    color: white;
    text-shadow: 2px 2px 5px rgba(0,0,0,.7);
  }
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;10_0&#x2F;10_0_cover_image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.5 released with GPG Commit Verification and Project Templates</title>
<release>9.5</release>
<link href='https://about.gitlab.com/releases/2017/08/22/gitlab-9-5-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/08/22/gitlab-9-5-released/</id>
<published>2017-08-22T00:00:00+00:00</published>
<author>
<name>Marcia Ramos</name>
</author>
<content type='html'>&lt;p&gt;Everything we do at GitLab, from our integrated product to our monthly releases, is centered on the goal of helping development teams reduce time to value.
With each release, we want to help you do more in less time, while also providing an intuitive and user-friendly experience in our product. GitLab 9.5 takes a big step in furthering this goal. This release features improvements to our navigation, new project templates with pre-configured CI, and new automation features for CI and performance monitoring that will save you time and effort.&lt;&#x2F;p&gt;

&lt;p&gt;This will be the last 9.x release, as we&#x27;re preparing to release
&lt;strong&gt;GitLab 10.0&lt;&#x2F;strong&gt; on September 22nd! Nonetheless, we&#x27;re shipping some great new features
to round off our 9.x releases:&lt;&#x2F;p&gt;


&lt;p&gt;To help improve your experience navigating GitLab, we&#x27;ve updated the &lt;a href=&quot;#new-navigation-improvements&quot;&gt;new navigation&lt;&#x2F;a&gt;,
streamlining the UI and reducing the number of clicks it takes to move through your GitLab instance. With the newly added icons and subnav on hover, it&#x27;s easier and faster than ever to explore GitLab.&lt;&#x2F;p&gt;

&lt;p&gt;Getting started on a new project just got faster. In GitLab 9.5, we&#x27;ve introduced &lt;a href=&quot;#project-templates&quot;&gt;Project Templates&lt;&#x2F;a&gt;,
which allow you to quickly create a new project that has CI pre-configured.&lt;&#x2F;p&gt;

&lt;p&gt;Continuing on our mission to save you time, we&#x27;ve made it possible for GitLab to &lt;a href=&quot;#automatic-retry-for-failed-ci-jobs&quot;&gt;automatically retry failed jobs&lt;&#x2F;a&gt;
ran with GitLab CI&#x2F;CD. Now, you don&#x27;t have to worry about losing time going back to your project&#x27;s pipelines just to hit retry on a failed job. 🙌&lt;&#x2F;p&gt;

&lt;p&gt;GitLab 9.5 also brings improvements to the latter part of the development lifecycle. With the addition of &lt;a href=&quot;#automatically-monitor-auto-deployed-apps&quot;&gt;Automatic Monitoring for Auto Deployed applications&lt;&#x2F;a&gt; we&#x27;ve made it easier for you to collect response and system metrics from your apps.&lt;&#x2F;p&gt;

&lt;p&gt;And last but not least, we&#x27;re shipping tons of &lt;a href=&quot;#performance-improvements&quot;&gt;performance improvements&lt;&#x2F;a&gt;
to continue to make GitLab faster than ever! 🚀 Enjoy!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_5&#x2F;9_5-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.4 released with Related Issues and Web Application Monitoring</title>
<release>9.4</release>
<link href='https://about.gitlab.com/releases/2017/07/22/gitlab-9-4-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/07/22/gitlab-9-4-released/</id>
<published>2017-07-22T00:00:00+00:00</published>
<author>
<name>Marcia Ramos</name>
</author>
<content type='html'>&lt;p&gt;Surprise is harder to achieve when you do everything in the open. But working in the
open gives us the power to tell you why we&#x27;re shipping what we&#x27;re releasing today and how
this release is setting up GitLab for something even better in the future.&lt;&#x2F;p&gt;


&lt;p&gt;GitLab 9.4 lays the foundation of much that is to come, while still giving you some
new powers today. You can now formally &lt;a href=&quot;#related-issues&quot;&gt;relate issues&lt;&#x2F;a&gt;
to each other, our out-of-the-box-magic monitoring now
&lt;a href=&quot;#web-application-monitoring&quot;&gt;collects many more metrics&lt;&#x2F;a&gt; without any
configuration and we&#x27;ve quadrupled the things you can do with variables in CI.&lt;&#x2F;p&gt;

&lt;p&gt;On top of this, we&#x27;re giving you an actual glimpse into the future with a opt-in
Beta of our &lt;a href=&quot;#new-navigation&quot;&gt;new navigation&lt;&#x2F;a&gt;. We hope that we can work with you to make it an
improvement everyone loves.&lt;&#x2F;p&gt;

&lt;p&gt;We are also thrilled to announce that we are shipping a &lt;a href=&quot;#gitlab-power-up-for-trello&quot;&gt;GitLab PowerUp for Trello&lt;&#x2F;a&gt;,
making it easy for you to integrate your Trello boards with GitLab! 🎉&lt;&#x2F;p&gt;

&lt;p&gt;Additionally, to empower our integrations set, we&#x27;re keen to make your life easier with
our new &lt;a href=&quot;#gitlab-slack-app-for-gitlab.com&quot;&gt;Slack App for GitLab.com&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;

&lt;p&gt;And if one glimpse doesn&#x27;t suffice, we&#x27;re aiming to
fully automate the configuration of your DevOps toolchain with the vision of &lt;strong&gt;Auto DevOps&lt;&#x2F;strong&gt;,
which will analyze your application and automatically configure your CI&#x2F;CD pipeline to build, test, and deploy to Kubernetes.
To see where we’re heading, check out
&lt;a href=&quot;&#x2F;blog&#x2F;whats-next-for-gitlab-ci&#x2F;#auto-devops-is-next&quot;&gt;our vision for Auto DevOps&lt;&#x2F;a&gt;!&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_4&#x2F;9_4-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.3 released with Code Quality and Multi-Project Pipeline Graphs</title>
<release>9.3</release>
<link href='https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/</id>
<published>2017-06-22T00:00:00+00:00</published>
<author>
<name>Fabio Busatto</name>
</author>
<content type='html'>&lt;p&gt;GitLab is an integrated product for the entire software development lifecycle.
With each monthly release, we work to bring more aspects of social coding,
continuous integration, release automation, and monitoring into a single tool.
With GitLab 9.3, we&#x27;re helping teams improve code quality, reduce cycle time and
make complex projects easier to manage.&lt;&#x2F;p&gt;


&lt;p&gt;GitLab 9.3 introduces &lt;a href=&quot;#gitlab-code-quality&quot;&gt;Code Quality&lt;&#x2F;a&gt; reports displayed directly in the Merge Request widget!
Code Quality gives you immediate insight into how a change will affect the health of your code and project.
This will reduce your review time and allow you to catch mistakes before merging a change.&lt;&#x2F;p&gt;

&lt;p&gt;Modern production-level software is often composed of many different projects,
especially those adopting micro-services architecture.
Therefore, understanding the relationships between these projects is crucial.
With GitLab 9.3, you can see how upstream and downstream project pipelines are linked together
with &lt;a href=&quot;#multi-project-pipeline-graphs&quot;&gt;Multi-Project Pipelines Graphs&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

&lt;p&gt;In addition, this release gives you an extremely powerful way to compare your usage of
each facet of GitLab with other people, using the &lt;a href=&quot;#conversational-development-index&quot;&gt;Conversational Development Index&lt;&#x2F;a&gt;.
The ConvDev Index gives you a quick overview of how you perform in going from Idea to Production and
where you have the opportunity to optimise.&lt;&#x2F;p&gt;

&lt;p&gt;To give you a quick idea of the power of GitLab, we&#x27;ve recorded a short demo that highlights
some of GitLab&#x27;s new features.
Enjoy the ability to have your entire development workflow in one single platform!&lt;&#x2F;p&gt;

&lt;figure class=&quot;video_container&quot;&gt;
  &lt;iframe src=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;embed&#x2F;IZ3ABxXMXMs&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;true&quot;&gt; &lt;&#x2F;iframe&gt;
&lt;&#x2F;figure&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_3&#x2F;9_3-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.2 released with Multiple Assignees for issues and Pipeline Schedules</title>
<release>9.2</release>
<link href='https://about.gitlab.com/releases/2017/05/22/gitlab-9-2-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/05/22/gitlab-9-2-released/</id>
<published>2017-05-22T00:00:00+00:00</published>
<author>
<name>Joshua Lambert</name>
</author>
<content type='html'>&lt;p&gt;GitLab is designed to allow everyone to contribute whether their teams are large or small, remote or in a single room.&lt;&#x2F;p&gt;

&lt;p&gt;As a new feature or product is moving from idea to production, often multiple people work on the same issue together. For example, it is not uncommon to have a front end developer, backend developer, UX designer, QA tester, and product manager teaming together to bring an idea to market. With 9.2, GitLab introduces &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;05&#x2F;22&#x2F;gitlab-9-2-released&#x2F;#multiple-assignees-for-issues&quot;&gt;Multiple Assignees for Issues&lt;&#x2F;a&gt; to streamline collaboration and allow these shared responsibilities to be clearly displayed. All assignees are shown across our workflows and receive notifications as they would before, simplifying communication and ownership.&lt;&#x2F;p&gt;


&lt;p&gt;GitLab 9.2 also lays the foundation for the localization of GitLab, with Cycle Analytics &lt;a href=&quot;#internationalized-cycle-analytics&quot;&gt;now available in Spanish and German&lt;&#x2F;a&gt; languages. In future releases we will continue to localize additional workflows within GitLab, to ensure that everyone can contribute regardless of their native language.&lt;&#x2F;p&gt;

&lt;p&gt;Developers also have additional control over when their CI&#x2F;CD Pipelines execute. We have added the ability to &lt;a href=&quot;#pipeline-schedules&quot;&gt;configure pipelines to run on a specific schedule&lt;&#x2F;a&gt; automating repetitive tasks like the creation of nightly builds, maintenance, or validation of external dependencies.&lt;&#x2F;p&gt;
&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_2&#x2F;9_2-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.1 released with Service Desk, Canary Deployments, and Burndown Charts</title>
<release>9.1</release>
<link href='https://about.gitlab.com/releases/2017/04/22/gitlab-9-1-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/04/22/gitlab-9-1-released/</id>
<published>2017-04-22T00:00:00+00:00</published>
<author>
<name>Victor Wu</name>
</author>
<content type='html'>
&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;p&gt;GitLab is designed to provide you &lt;em&gt;actionable feedback&lt;&#x2F;em&gt; in different stages of your
application lifecycle, and on different timescales.&lt;&#x2F;p&gt;

  &lt;p&gt;With 9.1, GitLab introduces &lt;a href=&quot;#canary-deployments-eep&quot;&gt;Canary Deployments&lt;&#x2F;a&gt;. This allows you
to deploy new code to a small portion of your fleet, providing you an opportunity
to revert with minimal impact if something goes wrong. If a problem is detected, you
can quickly revert, minimizing the impact on your users. This is &lt;em&gt;immediate production feedback&lt;&#x2F;em&gt;.&lt;&#x2F;p&gt;

  
  &lt;p&gt;As you expand your software products, GitLab&#x27;s new &lt;a href=&quot;#service-desk-eep&quot;&gt;Service Desk&lt;&#x2F;a&gt;
feature in 9.1 enables your growing user base to send emails to your team via a dedicated
address per project for any kind of feedback or support. These show up as GitLab confidential
issues in your project. Commenting on them responds back to the original email sender,
creating a brand new &lt;em&gt;integrated user feedback channel&lt;&#x2F;em&gt; right inside GitLab.&lt;&#x2F;p&gt;

  &lt;p&gt;GitLab 9.1 also introduces &lt;a href=&quot;#burndown-charts-ees&quot;&gt;Burndown Charts&lt;&#x2F;a&gt;, giving you &lt;em&gt;team development feedback&lt;&#x2F;em&gt;.
As a team, you can now visualize and track the pace of issue completion throughout
a milestone, giving you information to continuously make improvements in your processes
over time.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;twitter.com&#x2F;sytses&#x2F;status&#x2F;854453516672225280&quot;&gt;Heroku recently blogged&lt;&#x2F;a&gt; that GitLab CI (fully integrated into GitLab itself) has now
surpassed Travis CI in popularity based on Stack Overflow question popularity.
Google Trends also &lt;a href=&quot;https:&#x2F;&#x2F;trends.google.com&#x2F;trends&#x2F;explore?q=Travis%20CI,GitLab%20CI&quot;&gt;shows the same&lt;&#x2F;a&gt;.
In addition, GitLab is now &lt;a href=&quot;http:&#x2F;&#x2F;blog.bitrise.io&#x2F;2017&#x2F;01&#x2F;27&#x2F;state-of-app-development-in-2016.html#self-hosted&quot;&gt;used by two-thirds of the self-managed market&lt;&#x2F;a&gt;.
Thank you for the support! 👏 🙏&lt;&#x2F;p&gt;

  &lt;p class=&quot;text-center&quot;&gt;&lt;a href=&quot;&#x2F;events&#x2F;&quot; class=&quot;btn btn-lg btn-red webcast-button&quot;&gt;Join us for an upcoming event!&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;mvp gray-section&quot;&gt;
  &lt;div class=&quot;release-post-section&quot;&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;mvp_badge.png&quot; alt=&quot;mvp-badge&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h2 id=&quot;this-months-most-valuable-person-mvp-is-maxim-rydkin&quot;&gt;This month&#x27;s Most Valuable Person (&lt;a href=&quot;https:&#x2F;&#x2F;contributors.gitlab.com&#x2F;docs&#x2F;notable-contributors&quot;&gt;MVP&lt;&#x2F;a&gt;) is &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;innerwhisper&quot;&gt;Maxim Rydkin&lt;&#x2F;a&gt;&lt;&#x2F;h2&gt;

    &lt;p&gt;Maxim &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9362&quot;&gt;created a configuration setting&lt;&#x2F;a&gt; to
&lt;a href=&quot;#auto-cancel-redundant-pipelines-ce-ee&quot;&gt;automatically cancel pending pipelines if they are redundant&lt;&#x2F;a&gt;.
This is extremely helpful for when you push a change to GitLab, but want to quickly
push another small tweak shortly after.
This helps reduce time and precious system resources by canceling the unnecessary
pipelines.
Thank you Maxim!&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 id=&quot;service-desk-eep&quot;&gt;Service Desk eep&lt;&#x2F;h2&gt;

  &lt;p&gt;Service Desk is a powerful new feature that allows your team to connect directly with
any external party through email right inside of GitLab; no external tools required.
The ongoing and bi-directional conversation ensures that any user feedback is not
corrupted, helping you build the right features to solve your user&#x27;s real problems.&lt;&#x2F;p&gt;

  &lt;p&gt;Your customers or anyone in contact with the people in your project can email bugs,
feature requests, or any other general feedback directly into your GitLab project.
In turn, any GitLab users can respond straight from the project.&lt;&#x2F;p&gt;

  &lt;p&gt;As Service Desk is built right into GitLab itself, the complexity and inefficiencies
of multiple tools and external integrations are eliminated, significantly shortening
the cycle time from feedback to software update.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;service_desk_issue.png&quot; alt=&quot;Service Desk 1&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;Simply turn on the feature in a project&#x27;s settings, and you are provided a unique
email address to share with your users. Every time a user emails in feedback to that
address, GitLab automatically creates a confidential issue in that project. Subsequently,
your team adds comments to the issue, which automatically emails back the user. The
user can continue to follow up with responses in the email thread, and the entire
conversation is reflected inside the comment thread of the confidential issue.&lt;&#x2F;p&gt;

  &lt;p&gt;Your team stays inside that one confidential issue the whole time, enabling you to
leverage all the exiting powerful features of GitLab issue management as part of your
regular development workflows.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;service_desk_setting.png&quot; alt=&quot;Service Desk 2&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;Pro tip: Once you&#x27;ve deployed a new feature or bug fix to address a user&#x27;s feedback,
simply leave a comment in the confidential issue to inform the user that you&#x27;ve solved
their problem.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;service_desk.html&quot;&gt;Service Desk&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;canary-deployments-eep&quot;&gt;Canary Deployments eep&lt;&#x2F;h2&gt;

    &lt;p&gt;When embracing &lt;a href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Continuous_delivery&quot;&gt;Continuous Delivery&lt;&#x2F;a&gt;,
a company needs to decide what type of deployment strategy to use. One of the most
popular strategies is Canary Deployments, where a small portion of the fleet is
updated to the new version first. This subset, the canaries, then serve as the proverbial
&lt;a href=&quot;https:&#x2F;&#x2F;en.wiktionary.org&#x2F;wiki&#x2F;canary_in_a_coal_mine&quot;&gt;canary in the coal mine&lt;&#x2F;a&gt;.
If there is a problem with the new version of the application, only a small percentage
of users are affected and the change can either be fixed or quickly reverted.&lt;&#x2F;p&gt;

    &lt;p&gt;With GitLab 9.1 we are proud to announce first class support for
Canary Deployments on Kubernetes. For projects using
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html&quot;&gt;Auto Deploy&lt;&#x2F;a&gt;,
get started in less than a minute by simply switching to the updated Auto Deploy template.
Documentation is also available to walk through &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;deploy_boards.html#canary-deployments&quot;&gt;adding a canary stage&lt;&#x2F;a&gt; for those
who have written their own pipelines. As the pipeline executes Deploy Boards will
clearly mark canary pods, enabling quick and easy insight into the status of
each environment and deployment.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;deploy_boards.html#canary-deployments&quot;&gt;Canary Deployments&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;canary_deployments.png&quot; alt=&quot;image&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;burndown-charts-ees-eep&quot;&gt;Burndown Charts ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;We envision GitLab increasingly being able to help you to track and manage your work.
With this release, we are introducing burndown charts for projects.
This visualization helps you see how many issues are still incomplete as you progress
through a milestone, day by day.
You can see the remaining amount of issues (and even cumulative issue weight) &quot;burndown&quot;
over time, allowing you to make decisions earlier (on say, resources and scope) if
you see risks emerging from the chart.&lt;&#x2F;p&gt;

    &lt;p&gt;Any project milestone has a burndown chart as long as the milestone&#x27;s start date
and due date are set.
It&#x27;s conveniently located on the milestone page itself and indicates how many issues
(associated with that milestone) were or are still open for a given day in the milestone period.
The burndown chart can also be toggled to display the cumulative open issue weight for a given day.&lt;&#x2F;p&gt;

    &lt;p&gt;When using this feature, make sure your weights have been properly assigned, since
an open issue with no weight would contribute zero to the cumulative value.
We also took this opportunity to revamp the milestone page itself, simplifying the
look and feel to be more in line with the rest of GitLab.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;milestones&#x2F;#burndown-charts&quot;&gt;Burndown Charts&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;burndown_chart.png&quot; alt=&quot;Burndown Chart&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;protected-tags-ce-ees-eep&quot;&gt;Protected Tags ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;Tags can quickly get out of hand and, depending on your workflow, you might want to control who can create or update tags. Protected Tags in GitLab 9.1 does just that, making it easy to prevent tags from being created or updated.&lt;&#x2F;p&gt;

    &lt;p&gt;Using a very similar approach to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;repository&#x2F;branches&#x2F;protected.html&quot;&gt;protected branches&lt;&#x2F;a&gt;, you can now control this easily for any of your projects. Much like protected branches, you can define who is able to create tags and use wildcard matching on your rules too.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;protected_tags.html#protected-tags&quot;&gt;protected tags&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;protect-tags.png&quot; alt=&quot;Restrict Tags&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;recent-searches-ce-ees-eep&quot;&gt;Recent Searches ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;To quickly access frequent searches in issues and merge requests, we&#x27;ve added a convenient
dropdown menu that stores your most recent ones.
They are stored locally in your browser, with no manual configuration required.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;search&#x2F;#search-history&quot;&gt;Recent Searches&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;recent_searches.png&quot; alt=&quot;Recent Searches&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;discussions-in-merge-requests-and-issues-ce-ees-eep&quot;&gt;Discussions in Merge Requests and Issues ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;In merge requests, you&#x27;ve been able to start resolvable discussions by commenting
on a code diff. Starting in this release, you can start a resolvable discussion
in the main comment thread itself, without referring to any specific line of code.&lt;&#x2F;p&gt;

    &lt;p&gt;This is very useful if you have concerns about the entire merge request, and want
to leverage the existing features of
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;discussions&#x2F;#resolvable-discussions&quot;&gt;discussion resolution&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;In this release, we&#x27;ve applied this threaded concept to issue comments too.&lt;&#x2F;p&gt;

    &lt;p&gt;Collaboration in issues are meant to be a free-flowing exchange of ideas.
So, we&#x27;ve chosen to simply implement discussions in issues (without the
concept of resolvability).&lt;&#x2F;p&gt;

    &lt;p&gt;It will allow collaboration within GitLab to be even more flexible, but still
provide the structure for organization and review of ideas.&lt;&#x2F;p&gt;

    &lt;p&gt;Since collaboration also happens in commits and snippets, the same feature is
also available in those places too.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;discussions&#x2F;&quot;&gt;discussions in merge requests and issues&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;em&gt;Resolvable discussions in merge requests:&lt;&#x2F;em&gt;
&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;merge_request_resolvable_discussion.png&quot; alt=&quot;Merge Request Resolvable Discussion&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;em&gt;Discussions in issues:&lt;&#x2F;em&gt;
&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;issue_discussion.png&quot; alt=&quot;Issue Discussion&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;resolve-merge-request-discussion-with-new-issue-ce-ees-eep&quot;&gt;Resolve Merge Request Discussion with New Issue ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;In merge requests, you&#x27;ve been able to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;discussions&#x2F;#move-all-unresolved-discussions-in-a-merge-request-to-an-issue&quot;&gt;resolve all discussions at once by
creating a new issue&lt;&#x2F;a&gt;.
This is extremely helpful to defer problems but not lose track of them.&lt;&#x2F;p&gt;

    &lt;p&gt;In this release, we are providing more flexibility and granularity. You can now
resolve one individual discussion into a new issue, allowing you defer some problems
for later, and focus on the ones you need to solve now for this merge request.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;discussions&#x2F;#moving-a-single-discussion-to-a-new-issue&quot;&gt;resolving merge requests discussions with a new issue&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;issue_from_unresolved_discussion.png&quot; alt=&quot;Issue From Unresolved Discussion&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;microsoft-teams-integration-ce-ees-eep&quot;&gt;Microsoft Teams Integration ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;We want GitLab to be the most complete solution to get from idea to production
as quickly as possible. This means integrating into where conversation happens
and ideas are formed, be it Mattermost, Slack or Microsoft&#x27;s new Teams solution.&lt;&#x2F;p&gt;

    &lt;p&gt;Our first integration with Microsoft Teams introduces the ability to add
notifications for actions that happen on GitLab into a room on Microsoft
Teams using &lt;a href=&quot;https:&#x2F;&#x2F;msdn.microsoft.com&#x2F;en-us&#x2F;microsoft-teams&#x2F;connectors&quot;&gt;Office 365 Connectors&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;Any time you push to a project, create or update an issue or merge request
you can be notified in Teams. Want the output of your CI Pipeline - yip, that too!&lt;&#x2F;p&gt;

    &lt;p&gt;You&#x27;ll get a beautiful card in your room with all of the details on the
action performed, and links to jump into GitLab and find out more about
what&#x27;s been happening.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;integrations&#x2F;microsoft_teams.html&quot;&gt;Microsoft Teams Integration&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;microsoft-teams.png&quot; alt=&quot;Microsoft Teams&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;easier-file-templates-ce-ees-eep&quot;&gt;Easier File Templates ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;For a long time, we&#x27;ve had the ability to create file templates in GitLab.
For example, if you wanted to create a file for configuring Continuous Integration,
you could use a &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;yaml&#x2F;&quot;&gt;.gitlab-ci.yml&lt;&#x2F;a&gt; file. These
templates are now much easier to use in GitLab 9.1.&lt;&#x2F;p&gt;

    &lt;p&gt;When creating a new file or editing a file, you will now see a list of all
template types and template options as you can see in the screenshot below.
Changing a file template will replace the entire contents of the file in the editor,
but don&#x27;t worry, you can always undo this and get back to where you were!&lt;&#x2F;p&gt;

  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;easier-templates.png&quot; alt=&quot;Easier Templates&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;issue-title-auto-update-ce-ees-eep&quot;&gt;Issue Title Auto Update ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;As you use GitLab with a large number of users, data is constantly changing. With
this release, issue titles automatically update with no page refresh necessary.&lt;&#x2F;p&gt;

    &lt;p&gt;Many parts of the issue page and GitLab as a whole need improvements in this regard,
and we plan to do work on these in the coming releases.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;issue_title_realtime_update.gif&quot; alt=&quot;Issue Title Auto Update&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;
&lt;hr &#x2F;&gt;
&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;application-monitoring-ux-improvements-ce-ees-eep&quot;&gt;Application Monitoring UX Improvements ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;A number of minor changes have been made to application monitoring workflow, polishing the experience and making it easier to use.
We now have a beautiful getting started screen, can report additional troubleshooting information, and linked the performance charts to name just a few!&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;monitoring_ux.png&quot; alt=&quot;Monitoring UX Improvements&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;div class=&quot;release-post-section text-center zero-bottom-margin&quot;&gt;
  &lt;h2 id=&quot;other-improvements-in-gitlab-91&quot;&gt;Other Improvements in GitLab 9.1&lt;&#x2F;h2&gt;
&lt;&#x2F;div&gt;

&lt;section class=&quot;release-row align-top divider&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h3 id=&quot;simplified-approvals-settings-ees-eep&quot;&gt;Simplified Approvals Settings ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Merge request approvals allow you to block merges until the specified qualified users
or groups (and the number of them) have signed off (approved) them.
This is a crucial step of code review in many organizations.
As we continue to iterate on new functionality, we are simplifying the interface in
the project settings with this release, laying a foundation for high usability for
more powerful features in the future.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;approvals.png&quot; alt=&quot;Approvals&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;merge_requests&#x2F;approvals&#x2F;&quot;&gt;merge request approvals&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;improvements-to-disaster-recovery-in-alpha-eep&quot;&gt;Improvements to Disaster Recovery in Alpha eep&lt;&#x2F;h3&gt;

    &lt;p&gt;GitLab 9.1 ships with improvements to the Disaster Recovery feature
that we&#x27;ve released in &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;03&#x2F;22&#x2F;gitlab-9-0-released&#x2F;#disaster-recovery-alpha-eep&quot;&gt;GitLab 9.0 in Alpha&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;We&#x27;ve made it easier for &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-development-kit&#x2F;merge_requests&#x2F;270&quot;&gt;developers to work on the feature itself&lt;&#x2F;a&gt;.
We&#x27;ve also reduced the number of &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;issues&#x2F;1664&quot;&gt;steps required to set up Geo&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;Finally, we&#x27;ve added support for replicating the following types of files saved on disk: issue, merge request, and comment attachments, as well as user, group, and project avatars. We plan to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;issues&#x2F;846&quot;&gt;continue working actively on Disaster Recovery&lt;&#x2F;a&gt; in the coming releases.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;geo&#x2F;disaster_recovery&#x2F;index.html#gitlab-geo-disaster-recovery&quot;&gt;Disaster Recovery in Alpha&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;pipeline-mini-graph-added-to-commit-view-ce-ees-eep&quot;&gt;Pipeline mini-graph added to Commit View ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Pipeline mini-graphs now show in the system information box in commit views. Previously they were only shown in merge request views.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;mini_graph.png&quot; alt=&quot;Pipeline mini-graph&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;pipelines&#x2F;index.html#pipelines&quot;&gt;pipelines&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;notifications-for-successful-pipeline-now-off-by-default-ce-ees-eep&quot;&gt;Notifications for Successful Pipeline now Off by Default ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;We have changed the behavior of pipeline notifications in GitLab 9.1,
to reduce chatter and allow users additional control.
Notifications for successful pipelines will now be off by default,
and can be re-enabled by setting the notification level to Custom and
selecting &lt;code&gt;Successful pipeline&lt;&#x2F;code&gt;.
Additionally when selecting custom notifications for successful pipelines,
only the initiator of the pipeline will receive an email.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;profile&#x2F;notifications.html#notification-events&quot;&gt;pipeline notifications&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;system-note-icons-ce-ees-eep&quot;&gt;System Note Icons ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;As we add more features into GitLab, the historical view of system actions
recorded in the discussion threads of issues and merge requests becomes
increasingly important to know what has changed recently and further in the past.&lt;&#x2F;p&gt;

    &lt;p&gt;With this release, we are introducing icons next to system notes, to allow you to
easily demarcate system actions versus user comments. And this also allows you
to scan quickly through a long discussion thread and get a quick high-level
sense of how an object has evolved over time.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;system_notes.png&quot; alt=&quot;System Notes&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;usage-ping-ce-ees-eep&quot;&gt;Usage Ping ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;We’ve added the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;settings&#x2F;usage_statistics.html#usage-ping&quot;&gt;usage ping&lt;&#x2F;a&gt;,
already present in GitLab Enterprise Edition since version
&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;07&#x2F;22&#x2F;gitlab-8-10-released&#x2F;#usage-ping-ee-only&quot;&gt;8.10&lt;&#x2F;a&gt;,
to &lt;strong&gt;GitLab Community Edition&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;In the coming months, this will enable you to see
how your cohort usage compares to that of everyone else using GitLab.
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;30469&quot;&gt;See the issue on this effort&lt;&#x2F;a&gt; and
&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;31192&quot;&gt;the background of this project&lt;&#x2F;a&gt;.
You can see the exact payload that is being sent every week in &lt;strong&gt;admin&lt;&#x2F;strong&gt; &amp;gt; &lt;strong&gt;cohorts&lt;&#x2F;strong&gt;.
You can opt-out in &lt;strong&gt;admin&lt;&#x2F;strong&gt; &amp;gt; &lt;strong&gt;settings&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;usage_ping_optout.png&quot; alt=&quot;Usage Ping optout&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;usage_ping_json.png&quot; alt=&quot;Usage Ping JSON&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;settings&#x2F;usage_statistics.html#usage-ping&quot;&gt;usage ping&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;issue-boards-focus-mode-ees-eep&quot;&gt;Issue Boards Focus Mode ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;user&#x2F;project&#x2F;issue_board&#x2F;&quot;&gt;Issue Boards&lt;&#x2F;a&gt; are a great solution for planning and managing issues that are being
worked together by a team, allowing you to track them as they move from stage to stage
in your workflow.&lt;&#x2F;p&gt;

    &lt;p&gt;With this release, we are introducing focus mode in Issue Boards, which hides the
navigation UI when toggled on.&lt;&#x2F;p&gt;

    &lt;p&gt;This is helpful for co-located teams, when many folks are looking at a large screen
together during a collaboration session.
Just click the button at the top right of a board to toggle it on and off.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;issue_board_focus_mode.png&quot; alt=&quot;Issue Board Focus Mode&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;issue_board.html&quot;&gt;Issue Boards&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;projects-with-multiple-docker-images-ce-ees-eep&quot;&gt;Projects with Multiple Docker Images ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;In some situations, developers can create multiple containers based upon
the same code base. This can occur when building a container in an earlier stage
to be consumed in a later stage, or when packaging different versions of dependencies.&lt;&#x2F;p&gt;

    &lt;p&gt;As part of GitLab 9.1 the Container Registry now supports multiple image names
for a single project, allowing a simple way to store a project&#x27;s multiple containers.&lt;&#x2F;p&gt;

    &lt;p&gt;For example storing both &lt;code&gt;registry.example.com&#x2F;group&#x2F;project&#x2F;core:latest&lt;&#x2F;code&gt; and
&lt;code&gt;registry.example.com&#x2F;group&#x2F;project&#x2F;dependencies:latest&lt;&#x2F;code&gt; is now supported.&lt;&#x2F;p&gt;

    &lt;p&gt;Thanks &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;andrebsguedes&quot;&gt;André Guedes&lt;&#x2F;a&gt; for the fantastic contribution!&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;packages&#x2F;container_registry&#x2F;index.html#gitlab-container-registry&quot;&gt;Container Registry&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;!-- end of left column --&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;

    &lt;h3 id=&quot;auto-cancel-redundant-pipelines-ce-ees-eep&quot;&gt;Auto-cancel Redundant Pipelines ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;In situations where a number of commits occur within a short time period,
it is possible for multiple pipelines to be queued for the same branch.
Since pipelines are generally processed on a first come first serve basis,
pipelines will be ran for older commits first, even if they&#x27;ve already been
replaced. This can introduce delays in determining if the current branch is
passing tests, and is an inefficient use of CI runners.&lt;&#x2F;p&gt;

    &lt;p&gt;With GitLab 9.1, pipelines for older commits (specifically non-HEAD commits)
can now be automatically cancelled when a new pipeline is triggered for the
same branch; efficiently processing the queue and reducing the delay
in running the new (HEAD) pipeline.&lt;&#x2F;p&gt;

    &lt;p&gt;Only pending pipelines that haven&#x27;t started running yet will be auto-cancelled.
Any pipeline running when a new push comes in will continue to run until it finishes normally.&lt;&#x2F;p&gt;

    &lt;p&gt;If you want to enable this behavior, you can turn it on in the project&#x27;s CI&#x2F;CD Pipelines settings. Auto-cancellation will be on by default in a subsequent release.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;cancel_pipelines.png&quot; alt=&quot;Redundant Pipelines Cancelled&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;pipelines&#x2F;settings.html#auto-cancel-pending-pipelines&quot;&gt;automatically cancelling redundant pipelines&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;scheduled-pipelines-triggers-ce-ees-eep&quot;&gt;Scheduled Pipelines Triggers ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;With GitLab 9.1, we have added alpha support for scheduling a pipeline to run on a periodic basis. For example a daily pipeline can be run to check upstream dependencies, or to create a nightly package for broader testing. To configure a scheduled pipeline add a &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;triggers&#x2F;&quot;&gt;Pipeline Trigger&lt;&#x2F;a&gt;, edit it, and then enable &lt;code&gt;Schedule trigger&lt;&#x2F;code&gt;. Scheduling is set using the &lt;a href=&quot;https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Cron&quot;&gt;cron format&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;ci_schedule_trigger.png&quot; alt=&quot;Scheduled Pipeline Trigger&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;pipelines&#x2F;schedules.html&quot;&gt;scheduled pipeline triggers&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;improved-support-for-jobs-with-large-log-sizes-ce-ees-eep&quot;&gt;Improved Support for Jobs with Large Log Sizes ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;As part of our continued focus on improving performance, we have made
optimizations to how large job logs are handled. GitLab 9.1 will now only
display the last 500kb of a log when viewing a job, significantly improving
the responsiveness of the page and reducing bandwidth consumption.&lt;&#x2F;p&gt;

    &lt;p&gt;Because errors in a CI job typically occur near the end, it is often unnecessary
to send and display the entire log. This is especially important for larger
projects like Android, where a single job log can exceed 60mb. If further
analysis is needed, the complete log can always be downloaded by
clicking on the &lt;strong&gt;Download&lt;&#x2F;strong&gt; button.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;auto-deploy-enhancements-ce-ees-eep&quot;&gt;Auto Deploy Enhancements ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Along with support for &lt;a href=&quot;#canary-deployments-eep&quot;&gt;canary deployments&lt;&#x2F;a&gt;, we have made two other important enhancements to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html&quot;&gt;Auto Deploy&lt;&#x2F;a&gt;. First, we have added alpha support for applications that require a database, by automatically &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html#postgresql-database-support&quot;&gt;provisioning PostgreSQL&lt;&#x2F;a&gt; by default. Variables can be used to customize the credentials and database name, or if you&#x27;d like you can disable Postgres by setting &lt;code&gt;DISABLE_POSTGRES&lt;&#x2F;code&gt; to &lt;code&gt;yes&lt;&#x2F;code&gt;. Experimental support for &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html#private-project-support&quot;&gt;private projects&lt;&#x2F;a&gt; has also been added, allowing Kubernetes to authenticate and download the app&#x27;s container from the GitLab Container Registry.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about Auto Deploy&#x27;s &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html#private-project-support&quot;&gt;private project&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html#postgresql-database-support&quot;&gt;PostgreSQL database&lt;&#x2F;a&gt; support, and important limitations, in our docs.=&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;pipeline-list-now-refreshes-automatically-ce-ees-eep&quot;&gt;Pipeline list now refreshes automatically ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;As part of our on-going commitment to ensure our user experience is delightful, we have updated the pipeline overview page to refresh automatically. We will continue to update additional worfklows in subsequent releases, reducing the need to manually refresh.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;pipeline_refresh.png&quot; alt=&quot;Pipeline List Auto Refresh&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;pipelines&#x2F;index.html#pipelines&quot;&gt;pipelines&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;elasticsearch-improvements-ees-eep&quot;&gt;Elasticsearch Improvements ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;GitLab 9.1 EE introduces an experimental &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-elasticsearch-indexer&quot;&gt;repository indexer&lt;&#x2F;a&gt;.
This is a complete rewrite that&#x27;s four times faster! To enable it, just check the
box in the admin panel:&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_1&#x2F;elasticsearch_indexer.png&quot; alt=&quot;Elasticsearch Indexer&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;Send us your feedback - it should become the default indexer in the next few releases.
In addition, admins and auditors can now make use of global search functionality when
Elasticsearch is enabled, and code search results are highlighted again.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;integration&#x2F;elasticsearch.html#enable-elasticsearch&quot;&gt;Elasticsearch&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;gitlab-runner-91-changes-ce-ees-eep&quot;&gt;GitLab Runner 9.1 changes ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;We&#x27;re also releasing GitLab Runner 9.1 today.&lt;&#x2F;p&gt;

    &lt;h4 id=&quot;most-interesting-changes&quot;&gt;Most interesting changes&lt;&#x2F;h4&gt;

    &lt;ul&gt;
      &lt;li&gt;Extended verify command with runner selector (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;merge_requests&#x2F;532&quot;&gt;merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add log_level option to config.toml (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;merge_requests&#x2F;524&quot;&gt;merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Fix cache containers discovering regression (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;merge_requests&#x2F;534&quot;&gt;merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Cleanup and rename docker machine provider metrics (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;merge_requests&#x2F;531&quot;&gt;merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add histogram metrics for docker machine creation time (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;merge_requests&#x2F;533&quot;&gt;merge request&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
    &lt;&#x2F;ul&gt;

    &lt;p&gt;List of all changes can be found in GitLab Runner&#x27;s &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-runner&#x2F;blob&#x2F;v9.1.0&#x2F;CHANGELOG.md&quot;&gt;CHANGELOG&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;runner&#x2F;&quot;&gt;GitLab Runners&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;performance-improvements-ce-ees-eep&quot;&gt;Performance Improvements ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Making GitLab fast is always a priority.
Every release we are addressing performance improvements that make GitLab faster and
more reliable.
This will not only make self-managed GitLab CE and EE much faster, but also improve
the speed and reliability of &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&quot;&gt;GitLab.com&lt;&#x2F;a&gt; for everyone.&lt;&#x2F;p&gt;

    &lt;p&gt;In GitLab 9.1 we&#x27;ve nearly halved the amount of time taken to view a &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;27390&quot;&gt;list of projects&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;27166&quot;&gt;merge requests&lt;&#x2F;a&gt;, improved availability of &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;22940&quot;&gt;contribution analytics&lt;&#x2F;a&gt;, made &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;28183&quot;&gt;importing GitHub projects&lt;&#x2F;a&gt; faster and more reliable and have taken big steps towards upgrading GitLab with &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;26130&quot;&gt;zero downtime&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;Take a look at our full list of &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;issues?scope=all&amp;amp;state=closed&amp;amp;utf8=%E2%9C%93&amp;amp;milestone_title=9.1&amp;amp;label_name%5B%5D=performance&quot;&gt;performance improvements&lt;&#x2F;a&gt; in GitLab 9.1 and we&#x27;ve got a huge number of performance issues we will be addressing in &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;groups&#x2F;gitlab-org&#x2F;issues?label_name%5B%5D=performance&amp;amp;milestone_title=9.2&amp;amp;scope=all&amp;amp;state=all&quot;&gt;9.2&lt;&#x2F;a&gt; to keep making GitLab faster and more reliable.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;monitoring&#x2F;performance&#x2F;index.html#gitlab-performance-monitoring&quot;&gt;GitLab Performance Monitoring&lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;omnibus-package-improvements-ce-ees-eep&quot;&gt;Omnibus Package Improvements ce ees eep&lt;&#x2F;h3&gt;

    &lt;h4 id=&quot;suse-linux-enterprise-server-122&quot;&gt;SUSE Linux Enterprise Server 12.2&lt;&#x2F;h4&gt;
    &lt;p&gt;GitLab is now available on SUSE Linux Enterprise Server 12.2.
&lt;a href=&quot;&#x2F;install&#x2F;&quot;&gt;Read through the instructions&lt;&#x2F;a&gt;
to install.&lt;&#x2F;p&gt;

    &lt;h4 id=&quot;gitlab-mattermost-373&quot;&gt;GitLab Mattermost 3.7.3&lt;&#x2F;h4&gt;

    &lt;p&gt;GitLab 9.1 includes &lt;a href=&quot;https:&#x2F;&#x2F;about.mattermost.com&#x2F;&quot;&gt;Mattermost 3.7.3&lt;&#x2F;a&gt;, an open
source Slack-alternative providing workplace messaging for web, PC and phone
with archiving and search. Improvements this month include next generation
iOS and Android Apps in beta, new CLI integrations, and much more.
This version includes &lt;a href=&quot;http:&#x2F;&#x2F;about.mattermost.com&#x2F;security-updates&#x2F;&quot;&gt;security updates&lt;&#x2F;a&gt;
and upgrade is recommended.&lt;&#x2F;p&gt;

    &lt;p&gt;Mattermost 3.7.3 was also included in GitLab 9.0.4. Anyone on GitLab 9.0.4 or
later should have the patch already.&lt;&#x2F;p&gt;

    &lt;h4 id=&quot;other-improvements&quot;&gt;Other Improvements&lt;&#x2F;h4&gt;

    &lt;ul&gt;
      &lt;li&gt;GitLab now ships with Git 2.11
(&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;1903&quot;&gt;issue&lt;&#x2F;a&gt;).&lt;&#x2F;li&gt;
      &lt;li&gt;You can use Terraform configuration to spin up a GitLab instance on Google
Compute Engine (GCE) (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;1521&quot;&gt;issue&lt;&#x2F;a&gt;). Support for spinning up gitlab-runner is being worked on
(&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;2175&quot;&gt;issue&lt;&#x2F;a&gt;).&lt;&#x2F;li&gt;
      &lt;li&gt;Google Cloud Storage can now be used as the backend for the Container Registry
(&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;2076&quot;&gt;issue&lt;&#x2F;a&gt;).&lt;&#x2F;li&gt;
    &lt;&#x2F;ul&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
Learn more about &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;&quot;&gt;Omnibus GitLab &lt;&#x2F;a&gt; in our docs.&lt;&#x2F;p&gt;

    &lt;!-- end of right column --&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 class=&quot;text-center&quot; id=&quot;deprecations&quot;&gt;Deprecations&lt;&#x2F;h2&gt;

  &lt;h3 id=&quot;ubuntu-1204-package&quot;&gt;Ubuntu 12.04 Package&lt;&#x2F;h3&gt;

  &lt;p&gt;GitLab 9.1 will be the last release with support for Ubuntu 12.04 packages, as Ubuntu
12.04 will reach &lt;a href=&quot;http:&#x2F;&#x2F;fridge.ubuntu.com&#x2F;2017&#x2F;03&#x2F;15&#x2F;ubuntu-12-04-precise-pangolin-reaches-end-of-life-on-april-28-2017&#x2F;&quot;&gt;its End of Life in April 28th&lt;&#x2F;a&gt;. GitLab 9.2
will continue to be available on Ubuntu 14.04 and 16.04.&lt;&#x2F;p&gt;

  &lt;p&gt;Due: &lt;strong&gt;May 22nd&lt;&#x2F;strong&gt;, 2017.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;opensuse-132&quot;&gt;OpenSUSE 13.2&lt;&#x2F;h3&gt;

  &lt;p&gt;GitLab 9.1 will also be the last release with support for OpenSUSE 13.2 packages, as it
has reached its End of Life &lt;a href=&quot;https:&#x2F;&#x2F;en.opensuse.org&#x2F;Lifetime#Discontinued_distributions&quot;&gt;earlier this year&lt;&#x2F;a&gt;.
GitLab 9.2 will continue to be available on OpenSUSE 42.1.&lt;&#x2F;p&gt;

  &lt;p&gt;Due: &lt;strong&gt;May 22nd&lt;&#x2F;strong&gt;, 2017.&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;hr &#x2F;&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 class=&quot;text-center&quot; id=&quot;upgrade-barometer&quot;&gt;Upgrade Barometer&lt;&#x2F;h2&gt;

  &lt;p&gt;To upgrade to GitLab 9.1, no downtime is required.&lt;&#x2F;p&gt;

  &lt;p&gt;However there are some migrations that might take significant time depending on
your installation size:&lt;&#x2F;p&gt;

  &lt;ul&gt;
    &lt;li&gt;A new column is added to the users table which might take some time if you
have a lot of users.&lt;&#x2F;li&gt;
    &lt;li&gt;The old cache directory is removed, which might take some time if there were a
lot of uploaded files.&lt;&#x2F;li&gt;
  &lt;&#x2F;ul&gt;

  &lt;p&gt;Starting with GitLab 9.1.0 it&#x27;s possible to upgrade to a newer version of GitLab
without having to take your GitLab instance offline. However, for this to work
there are the following requirements:&lt;&#x2F;p&gt;

  &lt;ol&gt;
    &lt;li&gt;You can only upgrade 1 release at a time. For example, if 9.1.15 is the last
release of 9.1 then you can safely upgrade from that version to 9.2.0.
However, if you are running 9.1.14 you first need to upgrade to 9.1.15.&lt;&#x2F;li&gt;
    &lt;li&gt;You have to use &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;development&#x2F;database&#x2F;post_deployment_migrations.html&quot;&gt;post-deployment migrations&lt;&#x2F;a&gt;.&lt;&#x2F;li&gt;
    &lt;li&gt;You are using PostgreSQL. If you are using MySQL you will still need downtime
when upgrading.&lt;&#x2F;li&gt;
  &lt;&#x2F;ol&gt;

  &lt;p&gt;This applies to major, minor, and patch releases unless stated otherwise in a
release post.&lt;&#x2F;p&gt;

  &lt;p&gt;A new version of our API was released in &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;03&#x2F;22&#x2F;gitlab-9-0-released&#x2F;#api-v4&quot;&gt;GitLab 9.0&lt;&#x2F;a&gt;.
While existing calls to API v3 will continue to work until August 2017, we
advise you to make any necessary changes to applications that use the v3 API.
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;v3_to_v4.html&quot;&gt;Read the documentation&lt;&#x2F;a&gt; to learn
more.&lt;&#x2F;p&gt;

  &lt;h4 id=&quot;note&quot;&gt;Note&lt;&#x2F;h4&gt;

  &lt;p&gt;We assume you are upgrading from the latest version. If not, then also consult
the upgrade barometers of any intermediate versions you are skipping.
If you are upgrading from a GitLab version prior to 8.0 &lt;em&gt;and&lt;&#x2F;em&gt; you have CI
enabled, you have to upgrade to GitLab 8.0
&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;09&#x2F;22&#x2F;gitlab-8-0-released&#x2F;&quot;&gt;first&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;New configuration options have been introduced in the omnibus-gitlab packages.
To check what changed compared to your &lt;code&gt;&#x2F;etc&#x2F;gitlab&#x2F;gitlab.rb&lt;&#x2F;code&gt; configuration
file, run &lt;code&gt;sudo gitlab-ctl diff-config&lt;&#x2F;code&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;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 &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;update&#x2F;README.html&quot;&gt;&lt;code&gt;&#x2F;etc&#x2F;gitlab&#x2F;skip-auto-migrations&lt;&#x2F;code&gt;
file&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;end-of-deploy-boards-free-trial&quot;&gt;End of Deploy Boards Free Trial&lt;&#x2F;h3&gt;

  &lt;p&gt;To celebrate the launch of &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;03&#x2F;22&#x2F;gitlab-9-0-released&#x2F;#deploy-boards-eep&quot;&gt;Deploy Boards in GitLab 9.0&lt;&#x2F;a&gt;,
we offered a free trial to our Enterprise Edition Starter customers for the 9.0 release.
With the release of 9.1, Deploy Boards is now available only to Enterprise
Edition Premium customers. EEP customers should have already received an email
from GitLab Support with a new license key enabling this feature. If not,
please contact &lt;a href=&quot;&#x2F;support&#x2F;&quot;&gt;GitLab Support&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;gray-section&quot;&gt;
  &lt;div class=&quot;release-row align-top&quot;&gt;
    &lt;div class=&quot;column&quot;&gt;
      &lt;h3 id=&quot;changelog&quot;&gt;Changelog&lt;&#x2F;h3&gt;

      &lt;p&gt;Please check out the changelog to see all the named changes:&lt;&#x2F;p&gt;

      &lt;ul&gt;
        &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;blob&#x2F;master&#x2F;CHANGELOG.md&quot;&gt;GitLab CE&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
        &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;blob&#x2F;master&#x2F;CHANGELOG.md&quot;&gt;GitLab EE&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
      &lt;&#x2F;ul&gt;

      &lt;h3 id=&quot;installing&quot;&gt;Installing&lt;&#x2F;h3&gt;

      &lt;p&gt;If you are setting up a new GitLab installation please see the
&lt;a href=&quot;&#x2F;install&#x2F;&quot;&gt;download GitLab page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

      &lt;h3 id=&quot;updating&quot;&gt;Updating&lt;&#x2F;h3&gt;

      &lt;p&gt;Check out our &lt;a href=&quot;&#x2F;update&#x2F;&quot;&gt;update page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
    &lt;&#x2F;div&gt;
    &lt;div class=&quot;column&quot;&gt;
      &lt;h3 id=&quot;gitlab-products&quot;&gt;GitLab Products&lt;&#x2F;h3&gt;

      &lt;p&gt;We offer four different &lt;a href=&quot;&#x2F;stages-devops-lifecycle&#x2F;&quot;&gt;products&lt;&#x2F;a&gt; for you and your company:&lt;&#x2F;p&gt;

      &lt;ul&gt;
        &lt;li id=&quot;ce&quot;&gt;&lt;strong&gt;GitLab Community Edition (CE)&lt;&#x2F;strong&gt;: &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&quot;&gt;Open source&lt;&#x2F;a&gt;, self-managed solution of GitLab. Ideal for personal projects or small teams with minimal user management and workflow control needs. Every feature available in GitLab CE, is also available on GitLab Enterprise Edition (Starter and Premium), and GitLab.com.&lt;&#x2F;li&gt;
        &lt;li id=&quot;ee&quot;&gt;&lt;strong&gt;&lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;GitLab Enterprise Edition&lt;&#x2F;a&gt; (EE)&lt;&#x2F;strong&gt;: &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;&quot;&gt;Open core&lt;&#x2F;a&gt;, self-hosted, fully featured solution of GitLab. Available in two different subscriptions:
          &lt;ul&gt;
            &lt;li id=&quot;ees&quot;&gt;&lt;strong&gt;GitLab Enterprise Edition Starter (EES)&lt;&#x2F;strong&gt;: Ideal for co-located teams who need additional security and workflow controls for their professional projects.&lt;&#x2F;li&gt;
            &lt;li id=&quot;eep&quot;&gt;&lt;strong&gt;GitLab Enterprise Edition Premium (EEP)&lt;&#x2F;strong&gt;: Ideal for distributed teams who need advanced workflow controls, premium features, High Availability, and Premium Support.&lt;&#x2F;li&gt;
          &lt;&#x2F;ul&gt;
        &lt;&#x2F;li&gt;
        &lt;li id=&quot;gitlab-dot-com&quot;&gt;**&lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;GitLab.com&lt;&#x2F;a&gt; **: SaaS GitLab solution, with &lt;a href=&quot;&#x2F;pricing&#x2F;#gitlab-com&quot;&gt;free and paid subscriptions&lt;&#x2F;a&gt;. GitLab.com is hosted by GitLab, Inc. Ideal for individuals who want to get their projects up and running quickly. Administrated by GitLab (users don&#x27;t have access to admin settings).&lt;&#x2F;li&gt;
      &lt;&#x2F;ul&gt;

    &lt;&#x2F;div&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;p class=&quot;note text-center&quot;&gt;&lt;a href=&quot;https:&#x2F;&#x2F;www.pexels.com&#x2F;photo&#x2F;hot-air-balloons-landscape-adventure-aviation-7342&#x2F;&quot;&gt;Cover image&lt;&#x2F;a&gt; licensed under &lt;a href=&quot;https:&#x2F;&#x2F;www.pexels.com&#x2F;photo-license&#x2F;&quot;&gt;CC0&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;

&lt;style&gt;
  .badge-container a {
    margin-right: 3px;
  }
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_1&#x2F;9_1-cover-image.jpg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
<entry>
<title>GitLab 9.0 released with Subgroups and Deploy Boards</title>
<release>9.0</release>
<link href='https://about.gitlab.com/releases/2017/03/22/gitlab-9-0-released/' rel='alternate' />
<id>https://about.gitlab.com/releases/2017/03/22/gitlab-9-0-released/</id>
<published>2017-03-22T00:00:00+00:00</published>
<author>
<name>Victor Wu</name>
</author>
<content type='html'>
&lt;section class=&quot;release-post-section&quot;&gt;

  &lt;p&gt;Today we are releasing &lt;strong&gt;GitLab 9.0&lt;&#x2F;strong&gt;, 18 months after &lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;09&#x2F;22&#x2F;gitlab-8-0-released&#x2F;&quot;&gt;releasing 8.0&lt;&#x2F;a&gt;. We&#x27;ve made &lt;a href=&quot;&#x2F;releases&#x2F;&quot;&gt;significant advances to GitLab during this period&lt;&#x2F;a&gt;, shipping a version every single month on the 22nd. Let&#x27;s quickly recap how far we&#x27;ve come since 8.0, and see those features dovetailing into today&#x27;s 9.0 release. Or &lt;a href=&quot;#subgroups-ce-ee&quot;&gt;jump ahead&lt;&#x2F;a&gt; to 9.0 features.&lt;&#x2F;p&gt;

  
  &lt;hr &#x2F;&gt;

  &lt;h3 id=&quot;idea-to-production&quot;&gt;Idea to Production&lt;&#x2F;h3&gt;

  &lt;p&gt;In the last several releases, GitLab has transformed how development teams get from idea to production. In just a few minutes, you can deploy GitLab to a container scheduler, add CI&#x2F;CD with auto deployed review apps, utilize ChatOps, and analyze your cycle time. With 9.0 you can now watch your deploys with deploy boards and monitor application performance with Prometheus. Building on our &lt;a href=&quot;&#x2F;blog&#x2F;gitlab-master-plan&#x2F;&quot;&gt;Master Plan&lt;&#x2F;a&gt;, GitLab 9.0 truly delivers the entire DevOps toolchain, so let&#x27;s see how it all fits together:&lt;&#x2F;p&gt;

  &lt;figure class=&quot;video_container&quot;&gt;
    &lt;iframe src=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;embed&#x2F;PoBaY_rqeKA&quot; frameborder=&quot;0&quot; allowfullscreen=&quot;true&quot;&gt;&lt;&#x2F;iframe&gt;
  &lt;&#x2F;figure&gt;

  &lt;h3 id=&quot;usability-and-design&quot;&gt;Usability and Design&lt;&#x2F;h3&gt;

  &lt;p&gt;In &lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;09&#x2F;22&#x2F;gitlab-8-0-released&#x2F;&quot;&gt;8.0&lt;&#x2F;a&gt;, we refreshed GitLab&#x27;s look and feel, modernizing almost every UI element and significantly improving usability. (We had even updated our logo a few months prior.) Since then, we have continued to invest in design, ramping up our UX design and research &lt;a href=&quot;&#x2F;company&#x2F;team&#x2F;&quot;&gt;team&lt;&#x2F;a&gt;, who are dedicated to improving usability and solving major pain points, everything from small CSS tweaks, to major UX flows. In each 8.x release we have iteratively evolved the design. And with GitLab 9.0, we made huge strides in &lt;a href=&quot;#updated-navigation-ce-ee&quot;&gt;simplifying our global, group, and project navigation&lt;&#x2F;a&gt;, a crucial enhancement as GitLab&#x27;s feature set becomes increasingly powerful.&lt;&#x2F;p&gt;

  &lt;p&gt;In an effort to continue improving our UX, we now have a &lt;a href=&quot;&#x2F;community&#x2F;gitlab-first-look&#x2F;&quot;&gt;research panel&lt;&#x2F;a&gt; where you can help shape the future of GitLab! By joining our panel, you&#x27;ll be the first to see new features and your thoughts will drive product improvements!&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;a href=&quot;&#x2F;community&#x2F;gitlab-first-look&#x2F;&quot; class=&quot;btn btn-lg btn-red webcast-button&quot;&gt;Join our research panel&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;collaboration-on-digital-work&quot;&gt;Collaboration on Digital Work&lt;&#x2F;h3&gt;

  &lt;p&gt;GitLab helps you collaborate on digital work. We made many enhancements to issues, a core part of collaboration in GitLab. This includes weights (&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;12&#x2F;22&#x2F;gitlab-8-3-released&#x2F;#issue-weight-ee-only&quot;&gt;8.3&lt;&#x2F;a&gt;), linking to merge requests (&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;12&#x2F;22&#x2F;gitlab-8-3-released&#x2F;#merge-request-references-in-issues&quot;&gt;8.3&lt;&#x2F;a&gt;), moving an issue to another project (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;03&#x2F;22&#x2F;gitlab-8-6-released&#x2F;#move-issues-to-other-projects&quot;&gt;8.6&lt;&#x2F;a&gt;), and a powerful filter&#x2F;search interface (&lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;01&#x2F;22&#x2F;gitlab-8-16-released&#x2F;#new-issues-search-and-filter-interface&quot;&gt;8.16&lt;&#x2F;a&gt;). We also released issue boards (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;08&#x2F;22&#x2F;gitlab-8-11-released&#x2F;#issue-board&quot;&gt;8.11&lt;&#x2F;a&gt;), providing a simple mechanism for issue workflow management using stages (&quot;lists&quot;, in GitLab parlance). GitLab 9.0 continues to enhance boards further, &lt;a href=&quot;#boards-with-milestones-ees&quot;&gt;by improving its integration with milestones&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;We are excited to ship &lt;a href=&quot;#subgroups-ce-ee&quot;&gt;&lt;strong&gt;subgroups&lt;&#x2F;strong&gt; in GitLab 9.0&lt;&#x2F;a&gt;, another huge step in furthering GitLab collaboration. This powerful new paradigm of groups within groups allows for truly team-based and team-first collaboration in even very large organizations with many different departments. We&#x27;re on a &lt;a href=&quot;https:&#x2F;&#x2F;handbook.gitlab.com&#x2F;handbook&#x2F;company&#x2F;mission&#x2F;#mission&quot;&gt;mission&lt;&#x2F;a&gt; to enable &lt;strong&gt;everyone to contribute&lt;&#x2F;strong&gt;. 9.0 continues to help break down silos wherever you work so that indeed everyone in your organization can contribute.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;code-review-and-code-collaboration&quot;&gt;Code Review and Code Collaboration&lt;&#x2F;h3&gt;

  &lt;p&gt;We&#x27;ve continued to improve code review and code collaboration in GitLab since 8.0, including features such as merge when pipeline succeeds (&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;12&#x2F;22&#x2F;gitlab-8-3-released&#x2F;#auto-merge-on-build-success&quot;&gt;8.3&lt;&#x2F;a&gt;), code diffs (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;01&#x2F;22&#x2F;gitlab-8-4-released&#x2F;#code-highlighting-in-diffs&quot;&gt;8.4&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;02&#x2F;22&#x2F;gitlab-8-5-released&#x2F;#render-svgs-in-diffs&quot;&gt;8.5&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;04&#x2F;22&#x2F;gitlab-8-7-released&#x2F;#better-diffs&quot;&gt;8.7&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;07&#x2F;22&#x2F;gitlab-8-10-released&#x2F;#improved-diffs&quot;&gt;8.10&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;12&#x2F;22&#x2F;gitlab-8-15-released&#x2F;#diff-in-notification-emails&quot;&gt;8.15&lt;&#x2F;a&gt;), a conflict editor (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;08&#x2F;22&#x2F;gitlab-8-11-released&#x2F;#merge-conflict-resolution&quot;&gt;8.11&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;10&#x2F;22&#x2F;gitlab-8-13-released&#x2F;#merge-conflict-editor&quot;&gt;8.13&lt;&#x2F;a&gt;), merge request versions (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;09&#x2F;22&#x2F;gitlab-8-12-released&#x2F;#merge-request-versions&quot;&gt;8.12&lt;&#x2F;a&gt;), blocking merge until discussions resolved (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;11&#x2F;22&#x2F;gitlab-8-14-released&#x2F;#prevent-merge-until-review-is-done&quot;&gt;8.14&lt;&#x2F;a&gt;), toggling approvals (&lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;01&#x2F;22&#x2F;gitlab-8-16-released&#x2F;#removing-your-approval-in-ee-merge-requests&quot;&gt;8.16&lt;&#x2F;a&gt;), as well as squash and merge (&lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;02&#x2F;22&#x2F;gitlab-8-17-released&#x2F;#squash-and-merge-ee&quot;&gt;8.17&lt;&#x2F;a&gt;). Many of these and other features involve the merge request widget. So in GitLab 9.0, we are &lt;a href=&quot;#merge-request-widget-usability-ce-ee&quot;&gt;revamping its design&lt;&#x2F;a&gt; to accommodate the many existing and upcoming features that integrate with it.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;continuous-integration&quot;&gt;Continuous Integration&lt;&#x2F;h3&gt;

  &lt;p&gt;&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;09&#x2F;22&#x2F;gitlab-8-0-released&#x2F;#continuous-integration-in-gitlab&quot;&gt;8.0&lt;&#x2F;a&gt; was a pivotal release as it fully integrated continuous integration (CI) into GitLab itself. Subsequently, new CI features were implemented into the API (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;01&#x2F;22&#x2F;gitlab-8-4-released&#x2F;#new-ci-features-in-api&quot;&gt;8.4&lt;&#x2F;a&gt;) and pipeline events were exposed through webhooks (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;08&#x2F;22&#x2F;gitlab-8-11-released&#x2F;#pipelines-web-hooks&quot;&gt;8.11&lt;&#x2F;a&gt;). Pipelines were also integrated into merge requests (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;08&#x2F;22&#x2F;gitlab-8-11-released&#x2F;#pipelines-in-mrs&quot;&gt;8.11&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;02&#x2F;22&#x2F;gitlab-8-17-released&#x2F;#additional-pipeline-details-included-in-merge-request-workflow&quot;&gt;8.17&lt;&#x2F;a&gt;) and commits (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;10&#x2F;22&#x2F;gitlab-8-13-released&#x2F;#pipelines-for-commits&quot;&gt;8.13&lt;&#x2F;a&gt;), as well as its own visual graph (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;08&#x2F;22&#x2F;gitlab-8-11-released&#x2F;#pipelines-graph&quot;&gt;8.11&lt;&#x2F;a&gt;). GitLab runner was improved in every release from &lt;a href=&quot;&#x2F;releases&#x2F;&quot;&gt;8.10 to 8.17&lt;&#x2F;a&gt;. We released review apps (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;09&#x2F;22&#x2F;gitlab-8-12-released&#x2F;#review-apps-experimental&quot;&gt;8.12&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;10&#x2F;22&#x2F;gitlab-8-13-released&#x2F;#ability-to-stop-review-apps&quot;&gt;8.13&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;11&#x2F;22&#x2F;gitlab-8-14-released&#x2F;#review-apps&quot;&gt;8.14&lt;&#x2F;a&gt;) and auto deploy (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;12&#x2F;22&#x2F;gitlab-8-15-released&#x2F;#auto-deploy&quot;&gt;8.15&lt;&#x2F;a&gt;) to automatically deploy code into automatically created environments. And now with GitLab 9.0, we are shipping &lt;a href=&quot;#deploy-boards-eep&quot;&gt;deploy boards&lt;&#x2F;a&gt;, allowing you track how your app is being deployed to multiple servers.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;feedback-and-insight&quot;&gt;Feedback and Insight&lt;&#x2F;h3&gt;

  &lt;p&gt;GitLab also provides you feedback and insight into your code and development process. We released contribution analytics (&lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;12&#x2F;22&#x2F;gitlab-8-3-released&#x2F;#contribution-analytics-ee-only&quot;&gt;8.3&lt;&#x2F;a&gt;) and cycle analytics (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;09&#x2F;22&#x2F;gitlab-8-12-released&#x2F;#cycle-analytics&quot;&gt;8.12&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;10&#x2F;22&#x2F;gitlab-8-13-released&#x2F;#cycle-analytics-improvements&quot;&gt;8.13&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;11&#x2F;22&#x2F;gitlab-8-14-released&#x2F;#cycle-analytics-events&quot;&gt;8.14&lt;&#x2F;a&gt;). We released time tracking (&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;11&#x2F;22&#x2F;gitlab-8-14-released&#x2F;#time-tracking-beta-ee&quot;&gt;8.14&lt;&#x2F;a&gt;, &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;01&#x2F;22&#x2F;gitlab-8-16-released&#x2F;#time-tracking-in-ce-and-api&quot;&gt;8.16&lt;&#x2F;a&gt;). In &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;01&#x2F;22&#x2F;gitlab-8-16-released&#x2F;#monitoring-gitlab-with-prometheus&quot;&gt;8.16&lt;&#x2F;a&gt; and &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;02&#x2F;22&#x2F;gitlab-8-17-released&#x2F;#monitoring-gitlab-with-prometheus&quot;&gt;8.17&lt;&#x2F;a&gt;, we shipped open source &lt;a href=&quot;https:&#x2F;&#x2F;prometheus.io&quot;&gt;Prometheus&lt;&#x2F;a&gt; to extend that feedback into monitoring the server that hosts your GitLab instance, through the Prometheus console. In GitLab 9.0, we are releasing &lt;a href=&quot;#environment-monitoring-ce-ee&quot;&gt;environment monitoring&lt;&#x2F;a&gt; integrated into the GitLab UI itself, building on top of the Prometheus foundation.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;thank-you&quot;&gt;Thank You&lt;&#x2F;h3&gt;

  &lt;p&gt;We&#x27;re humbled by our community continuing to actively create and comment in numerous issues, as well as directly contributing source code. &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests?label_name%5B%5D=Community+Contribution&amp;amp;milestone_title=9.0&amp;amp;scope=all&amp;amp;state=merged&quot;&gt;In 9.0, there are over 130 merge requests from the community&lt;&#x2F;a&gt;, with &lt;a href=&quot;#notable-community-contributions-ce&quot;&gt;many notable contributions&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;As an open source project, GitLab CE now has over &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;commits&#x2F;master&quot;&gt;47,000 commits&lt;&#x2F;a&gt; (more than doubling the &lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;10&#x2F;22&#x2F;gitlab-8-1-released&#x2F;&quot;&gt;20,000 count set back in 8.1&lt;&#x2F;a&gt;). Today, GitLab has &lt;a href=&quot;http:&#x2F;&#x2F;contributors.gitlab.com&quot;&gt;over 1,500 contributors&lt;&#x2F;a&gt;. Thank you! 👏🙏&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;growth&quot;&gt;Growth&lt;&#x2F;h3&gt;

  &lt;p&gt;We&#x27;ve also grown quickly during this time. We had just under 25 team members in 7 countries when we shipped 8.0. Today, we have &lt;a href=&quot;&#x2F;company&#x2F;team&#x2F;&quot;&gt;over 150 folks spread across 37 countries&lt;&#x2F;a&gt;. That has helped us now to ship self-managed GitLab in three versions, &lt;a href=&quot;&#x2F;stages-devops-lifecycle&#x2F;&quot;&gt;Community Edition (CE), Enterprise Edition Starter (EES), and Enterprise Edition Premium (EEP)&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;unique-platform&quot;&gt;Unique Platform&lt;&#x2F;h3&gt;

  &lt;p&gt;Over the past years we’ve seen application lifecycle management (ALM) tools
move into the direction of offering a single, integrated experience. GitLab is
at the forefront of this and we&#x27;re now shipping with monitoring by default, completing our &lt;a href=&quot;&#x2F;direction&#x2F;#scope&quot;&gt;scope&lt;&#x2F;a&gt;.
If you want to design, code, build, deploy, and
monitor an application, you can now all do that straight from within GitLab.&lt;&#x2F;p&gt;

  &lt;p&gt;GitLab is a complete and opinionated application lifecycle management tool with
one interface and one data-store. GitLab’s integrated approach brings emergent
benefits such as shorter time to market (measurable through cycle analytics),
higher developer efficiency, and a consistent development process.&lt;&#x2F;p&gt;

  &lt;p&gt;Enjoy 9.0 and read on for details!&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=rEChfZEsuVw&amp;amp;feature=youtu.be&quot; class=&quot;btn btn-lg btn-red&quot;&gt;Watch our release webcast!&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;gitlab-90-meetups&quot;&gt;GitLab 9.0 Meetups&lt;&#x2F;h3&gt;

  &lt;p&gt;Let&#x27;s get together and talk about all the awesomeness coming with GitLab 9.0. We&#x27;ll be in San Francisco,
Denver, Boston, Amsterdam, London, and New Orleans. 🙌&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;a href=&quot;&#x2F;events&#x2F;&quot; class=&quot;btn btn-lg btn-red&quot;&gt;Join GitLab Meetups&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;mvp gray-section&quot;&gt;
  &lt;div class=&quot;release-post-section&quot;&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;mvp_badge.png&quot; alt=&quot;mvp-badge&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h2 id=&quot;this-months-most-valuable-person-mvp-is-jacopo-beschi&quot;&gt;This month&#x27;s Most Valuable Person (&lt;a href=&quot;https:&#x2F;&#x2F;contributors.gitlab.com&#x2F;docs&#x2F;notable-contributors&quot;&gt;MVP&lt;&#x2F;a&gt;) is &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;jacopo-beschi&quot;&gt;Jacopo Beschi&lt;&#x2F;a&gt;&lt;&#x2F;h2&gt;

    &lt;p&gt;Jacopo made it possible to &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8691&quot;&gt;undo marking a todo item as done in the todos list&lt;&#x2F;a&gt;. This is a huge productivity enhancement that helps you recover from mistakes in managing todos. Thanks Jacopo!&lt;&#x2F;p&gt;

  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;

  &lt;h2 id=&quot;subgroups-ce-ees-eep&quot;&gt;Subgroups ce ees eep&lt;&#x2F;h2&gt;

  &lt;p&gt;GitLab has always been the simplest way for people to collaborate on code in a project. Just create a project, and you&#x27;re on your way from idea to production. Users have &lt;em&gt;also&lt;&#x2F;em&gt; told us that they want GitLab to be a team-based collaboration tool that supports hierarchical team structures sharing different code repositories. With 9.0, we are excited to ship our brand new version of GitLab groups that allows for groups within groups, i.e. &quot;subgroups&quot;.&lt;&#x2F;p&gt;

  &lt;p&gt;Each group, at each level, is itself a first-class citizen GitLab group, with the ability to have multiple projects. The new version of groups thus enables you to have a hierarchy of code repositories. You can create up to 20 levels of subgroups, giving you an incredible level of flexibility.&lt;&#x2F;p&gt;

  &lt;p&gt;In this example, the organization represented by the &lt;code&gt;gitlab-nested&lt;&#x2F;code&gt; group has a design team, a backend team, and a frontend team, each represented by a group within the &lt;code&gt;gitlab-nested&lt;&#x2F;code&gt; group. The &lt;code&gt;design&lt;&#x2F;code&gt; and &lt;code&gt;backend&lt;&#x2F;code&gt; groups have further subgroups within them.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;gitlab-nested.png&quot; alt=&quot;Subgroups&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;Feel free to look at and provide feedback on what we are working on for &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues?label_name%5B%5D=subgroups&quot;&gt;groups in future releases of GitLab&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;group&#x2F;subgroups&#x2F;&quot;&gt;Learn more about subgroups in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;deploy-boards-eep&quot;&gt;Deploy Boards eep&lt;&#x2F;h2&gt;

    &lt;p&gt;GitLab has an incredibly powerful CI&#x2F;CD system, with over a thousand runners executing pipelines for GitLab.com projects alone. These pipelines perform builds to compile and package software, run automated tests, spawn review apps, and can even deploy software to staging and production. To date, these deployments would report back whether the environment was successfully updated, but what if you wanted more fidelity? Or a single pane to view all deployments across all environments? For larger organizations, the answers to these questions become particularly important.&lt;&#x2F;p&gt;

    &lt;p&gt;Today with 9.0, we are excited to release Deploy Boards for environments running on Kubernetes. The Environments page of Pipelines now offers a single place to view the current health and deployment status of each environment, displaying the specific status of each pod in the deployment. Developers and other teammates can view the progress and status of a rollout, pod by pod, in the workflow they already use without any need to access Kubernetes.&lt;&#x2F;p&gt;

    &lt;p&gt;To celebrate the launch, Deploy Boards will be available in 9.0 as a free trial for Enterprise Edition Starter customers.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;deploy_boards.html&quot;&gt;Learn more about Deploy Boards in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;deploy_boards.png&quot; alt=&quot;Deploy Boards&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;export-issues-ees-eep&quot;&gt;Export Issues ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;GitLab already enables you to filter, search, and navigate through the many issues you use daily. But users say they want a snapshot of issues for offline analysis or to communicate with other teams who may not be in GitLab just yet. With 9.0 EES, GitLab will email you a CSV export of issues if you click the download button at the top right in the issue list view.&lt;&#x2F;p&gt;

    &lt;p&gt;We designed and integrated the feature directly into the project issue list view. This allows you to leverage the existing powerful filter and search capability so that you can export exactly just the issues you care about. The actual processing and email sending happens asynchronously in the background once you confirm the action, so that it gets out of your way and you can continue to use GitLab as normal.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;issues&#x2F;csv_export.html&quot;&gt;Learn more about exporting issues in CSV in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;export_issues.png&quot; alt=&quot;Export Issues&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;environment-monitoring-ce-ees-eep&quot;&gt;Environment Monitoring ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;A robust monitoring infrastructure is crucial to operating a successful application.  It ensures your app is responsive, provides valuable insight into the impact of changes, and enables quick debugging when problems occur. However setting this infrastructure up is often a lower priority, in particular for non-production environments, and it is often not integrated with the rest of your toolchain.&lt;&#x2F;p&gt;

    &lt;p&gt;With GitLab 9.0, we are proud to introduce the first monitoring system that is fully integrated with your CI&#x2F;CD pipelines and source code repository. Leveraging &lt;a href=&quot;https:&#x2F;&#x2F;prometheus.io&quot;&gt;Prometheus&lt;&#x2F;a&gt;, GitLab will now bring the same technology used for production systems to development environments like staging and even review apps.&lt;&#x2F;p&gt;

    &lt;p&gt;In this initial release we are tracking the CPU and Memory utilization of your app running on each Kubernetes based environment, and this is only the beginning. In the near feature we will gauge the performance impact of a merge, support a much broader range of application metrics, and fuse monitoring data with Deploy Boards.&lt;&#x2F;p&gt;

    &lt;p&gt;Participate in the discussion and future of performance monitoring with GitLab &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues?scope=all&amp;amp;utf8=✓&amp;amp;state=opened&amp;amp;label_name[]=Prometheus&amp;amp;label_name[]=feature%20proposal&quot;&gt;here&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;integrations&#x2F;prometheus.html&quot;&gt;Learn more about the Prometheus project integration in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;prometheus.png&quot; alt=&quot;Environment monitoring with Prometheus&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h2 id=&quot;performance-improvements-ce-ees-eep&quot;&gt;Performance Improvements ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;As with every release, we&#x27;ve worked hard to make GitLab faster. With 9.0 in particular, we&#x27;ve put a particular focus on noticeable performance improvements across the board. Elasticsearch (ES) gets an upgrade in GitLab EE 9.0, with support for ES 5.1 and a host of smaller fixes. In accordance with our &quot;cloud native&quot; philosophy, we&#x27;ve added support for &lt;a href=&quot;https:&#x2F;&#x2F;aws.amazon.com&#x2F;elasticsearch-service&#x2F;&quot;&gt;AWS-hosted&lt;&#x2F;a&gt; and HTTPS Elasticsearch clusters. Larger GitLab EE installations will benefit from improvements in the initial indexing process, and minor performance improvements have been made to repository indexing.&lt;&#x2F;p&gt;

    &lt;p&gt;The improvements to the dashboards were focused on &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9030&quot;&gt;more efficient searching by author or assignee&lt;&#x2F;a&gt;, and &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9006&quot;&gt;removing unnecessary queries&lt;&#x2F;a&gt;. As the most common use for the dashboard is to view issues or merge requests assigned to you, this should be noticeable for most users. On GitLab.com, we saw transaction timings drop significantly for issues and merge requests.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues?label_name%5B%5D=performance&amp;amp;milestone_title=9.0&amp;amp;scope=all&amp;amp;state=closed&quot;&gt;Take a look&lt;&#x2F;a&gt; at the full list of performance improvements in 9.0 and keep an eye out for further improvements in upcoming releases as GitLab continues to get faster, especially for large installations.&lt;&#x2F;p&gt;

    &lt;p&gt;Did you know, &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&quot;&gt;GitLab.com&lt;&#x2F;a&gt; is &quot;merely&quot; a massive-scale implementation of GitLab EE with hundreds of thousands of users? This just shows the level of scale that you can run GitLab EE and these performance improvements should start making a noticeable difference to the speed and reliability of GitLab.com.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;issues_dashboard.png&quot; alt=&quot;Issues dashboard&quot; &#x2F;&gt;&lt;em class=&quot;shadow&quot;&gt;Transaction timings dropping significantly for issues dashboard&lt;&#x2F;em&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;merge_requests_dashboard.png&quot; alt=&quot;Merge requests dashboard&quot; &#x2F;&gt;&lt;em class=&quot;shadow&quot;&gt;Transaction timings dropping significantly for merge requests dashboard&lt;&#x2F;em&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;database-load-balancing-ees-eep&quot;&gt;Database Load Balancing ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;Load balancing of database queries allows one to spread the load and impact of
queries across multiple database servers. Traditionally this involves additional
software such as &lt;a href=&quot;http:&#x2F;&#x2F;www.pgpool.net&#x2F;&quot;&gt;pgpool&lt;&#x2F;a&gt;. Starting with 9.0, GitLab
Enterprise Edition supports load balancing of queries when using PostgreSQL.&lt;&#x2F;p&gt;

    &lt;p&gt;Load balancing queries can bring many benefits, such as reducing the load and
memory usage of the primary, and reducing response timings. Spreading the load
also means that badly behaving database queries will not impact queries
executing on a different database server, reducing the likelihood of such
queries negatively affecting a GitLab installation.&lt;&#x2F;p&gt;

    &lt;p&gt;GitLab&#x27;s load balancer also responds to database failovers. When a primary is
unresponsive or was changed to a secondary, the load balancer will wait a brief
moment before retrying an operation. When secondaries become unavailable, they
are ignored until they become available again. For this to work in the most
transparent way you will need to use a load balancer (e.g. HAProxy) for every
database host.&lt;&#x2F;p&gt;

    &lt;p&gt;One problem of load balancing is dealing with replication lag. For example, if a
write happens and you then read from a secondary it&#x27;s possible for said
secondary to not yet have the data. One way of dealing with this is to use
synchronous replication. However, synchronous replication is not ideal as
replication lag could cause queries to take a very long time. Furthermore, if a
replica were to become unavailable the whole system can grind to a halt.&lt;&#x2F;p&gt;

    &lt;p&gt;To work around this the database load balancer uses &quot;sticky sessions&quot;. When a
user triggers a write to the primary the user&#x27;s session will keep using the
primary. Session sticking is disabled again once a timeout expires (30 seconds),
or when the written data is available on all secondaries.&lt;&#x2F;p&gt;

    &lt;p&gt;For more information on how to set up database load balancing you can refer to
the documentation section &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;database_load_balancing.html&quot;&gt;&quot;Database Load Balancing&quot;&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;load_balancing_load.png&quot; alt=&quot;Load Balancing Load&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;load_balancing_memory_usage.png&quot; alt=&quot;Load Balancing Memory Usage&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;load_balancing_timing_improvements.png&quot; alt=&quot;Load Balancing Timing Improvements&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;

  &lt;h2 id=&quot;updated-navigation-ce-ees-eep&quot;&gt;Updated Navigation ce ees eep&lt;&#x2F;h2&gt;

  &lt;p&gt;Here at GitLab, most of our business functions (not just product development) occur on GitLab.com itself. So we definitely understand the importance of navigation. We want to make it frictionless, intuitive, and efficient for you to perform your daily tasks, especially if you are using GitLab for several hours each day.&lt;&#x2F;p&gt;

  &lt;p&gt;Navigation design is a crucial component in achieving that, and with 9.0, we have modernized the interface, leveraging best practices from our design team, as well as incorporating feedback from user research. At first glance, it doesn&#x27;t seem like a lot has changed. But that was intentional. We meticulously analyzed what was already working well, and changed only the problem areas.&lt;&#x2F;p&gt;

  &lt;p&gt;The menu items in the tabbed navigation interface have been re-arranged (and in some cases, merged and renamed) for both the main and subtabs. The activity tab is now a subtab of the project tab. The main tabs of repository, issues, merge requests, and pipelines and now positioned from left to right in that order, reflecting the idea to production flow. The subtabs in the main graph tab have been re-arranged and placed in other locations. Again, we carefully considered where each menu should be located drawing from feedback and analysis. &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;26348&quot;&gt;Read more about the details of the change.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;Another notable change is the pop-in sidebar. That has been now replaced by a less intrusive dropdown menu in the top left, that doesn&#x27;t unnecessarily cover too much screen content. Previously there was a dropdown menu for settings, accessed from a cog icon at the top right for the project and group pages. These have been now pulled into the existing tabbed menu interface, harmonizing and simplifying the entire experience.&lt;&#x2F;p&gt;

  &lt;p&gt;In 9.0, we simplified the project view configuration settings so that you can now choose between viewing (1) Files and README or (2) Activity on the main project tab for any project. (This is a profile setting that applies to all projects you view.) The first option is the default. Previously, we had a third option for viewing just the README, which was the default. We wanted something that was helpful for both new and existing users, and based on user feedback and research, we are opting for this design.&lt;&#x2F;p&gt;

  &lt;p&gt;We also brought back the ability the create a new project quickly, by simply clicking the &lt;code&gt;+&lt;&#x2F;code&gt; button at the top right.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;navigation.png&quot; alt=&quot;Navigation&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;

    &lt;h2 id=&quot;reorder-issues-in-board-list-ce-ees-eep&quot;&gt;Reorder Issues in Board List ce ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;user&#x2F;project&#x2F;issue_board&#x2F;&quot;&gt;Issue Boards&lt;&#x2F;a&gt; are a great way to manage issues moving through the different stages (&quot;lists&quot; in GitLab), in order to quickly get an idea to production. But users often want to further represent order or priority of issues within a single list. With 9.0, you can now reorder issues within an issue board list, using the intuitive and existing drag and drop mechanism.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;issue_board.html&quot;&gt;Learn more about Issue Boards for Community Edition in our docs&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;boards_reorder.gif&quot; alt=&quot;Boards Reorder&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row image-left&quot;&gt;
  &lt;div class=&quot;column text-column&quot;&gt;
    &lt;h2 id=&quot;boards-with-milestones-ees-eep&quot;&gt;Boards with Milestones ees eep&lt;&#x2F;h2&gt;

    &lt;p&gt;A GitLab Issue Board enables you to manage a group of issues within a single milestone, but requires you to select the associated milestone filter each time you navigate to it. With GitLab 9.0 EES, you can now create an Issue Board that is associated to a specific milestone. This allows you to create unique boards for individual milestones.&lt;&#x2F;p&gt;

    &lt;p&gt;As you plan and execute work in each new milestone, we suggest you keep creating new boards. This allows you to conveniently straddle between milestones, while also allowing you to save and look back at previous completed milestones.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;issue_board.html&quot;&gt;Learn more about Issue Boards for Enterprise Edition in our docs&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;

  &lt;div class=&quot;column image-column&quot;&gt;
    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;boards_milestone.gif&quot; alt=&quot;Boards Milestone&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 id=&quot;api-v4-ce-ees-eep&quot;&gt;API v4 ce ees eep&lt;&#x2F;h2&gt;

  &lt;p&gt;Our &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;&quot;&gt;API&lt;&#x2F;a&gt; is a great way to automate tasks, control and automate GitLab in new and powerful ways. Over time, we have continued to improve our API to make it more complete and support the new features we add every month to make GitLab the best end-to-end development environment.&lt;&#x2F;p&gt;

  &lt;p&gt;This constant iteration has resulted in a few inconsistencies in our existing API. Today we are announcing v4 of our API, which aims to make the API more consistent and more RESTful.&lt;&#x2F;p&gt;

  &lt;p&gt;We will continue to support v3 of the API until August 2017 and so we encourage you to make any necessary changes to applications that use the v3 API.&lt;&#x2F;p&gt;

  &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;v3_to_v4.html&quot;&gt;Take a look at the changes in v4 to see what&#x27;s different.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 id=&quot;disaster-recovery-alpha-eep&quot;&gt;Disaster Recovery Alpha eep&lt;&#x2F;h2&gt;

  &lt;p&gt;Regardless of the size of your company, you need to make sure that your
infrastructure is resilient to any kind of natural or human-induced disasters
that can happen. One of the best practices in this case is to have a least two
servers (one primary, one secondary) in two different locations to make sure
that if the primary server goes down, the other one can take over. Having this
in place is critical for any teams to make sure you reduce the downtime as much
as possible, and reduce the risk of data loss. We have received many requests to
offer a disaster recovery solution built in GitLab and today we are introducing
a first step towards supporting this.&lt;&#x2F;p&gt;

  &lt;p&gt;Since &lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;02&#x2F;22&#x2F;gitlab-8-5-released&#x2F;&quot;&gt;GitLab 8.5&lt;&#x2F;a&gt;,
GitLab ships with &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;administration&#x2F;geo&#x2F;&quot;&gt;Geo&lt;&#x2F;a&gt;, a
feature that lets you have one or more secondary instances that mirror your main
GitLab instance. Geo&#x27;s primary goal was to drastically speed up cloning and
fetching projects over large distances. While Geo works really well for this
use case, it has one point that prevents us to use this technology to support a
full disaster recovery scenario: files that are saved on disk were not
replicated.&lt;&#x2F;p&gt;

  &lt;p&gt;This is &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;issues&#x2F;846&quot;&gt;what we are actively working on&lt;&#x2F;a&gt;
and with GitLab 9.0, we are releasing a first step towards providing support for
Disaster Recovery scenarios. We call it Disaster Recovery in Alpha. A bunch of
important changes to Geo have been introduced with this release:&lt;&#x2F;p&gt;

  &lt;ul&gt;
    &lt;li&gt;If you use LFS, LFS objects will automatically be replicated to the secondary
nodes (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;merge_requests&#x2F;1237&quot;&gt;Merge request&lt;&#x2F;a&gt;).&lt;&#x2F;li&gt;
    &lt;li&gt;All file uploads are now recorded in the database
(&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8893&quot;&gt;Merge request&lt;&#x2F;a&gt;).
This will allow us to replicate those files in a future iteration.&lt;&#x2F;li&gt;
    &lt;li&gt;There is a new process to automatically backfill repositories
(&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;merge_requests&#x2F;1197&quot;&gt;Merge request&lt;&#x2F;a&gt;).&lt;&#x2F;li&gt;
    &lt;li&gt;You can now disable a secondary node through the UI.&lt;&#x2F;li&gt;
    &lt;li&gt;Both GitLab Geo and Disaster Recovery are under development and not production-ready.&lt;&#x2F;li&gt;
  &lt;&#x2F;ul&gt;

  &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;geo_dr.png&quot; alt=&quot;Navigation&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

  &lt;p&gt;To enable Disaster Recovery in Alpha, refer to &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;geo&#x2F;replication&#x2F;configuration.html&quot;&gt;the documentation&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;Disaster Recovery in Alpha is available to all Enterprise Edition Premium
customers as part of GitLab Geo.&lt;&#x2F;p&gt;

  &lt;p&gt;On a sidenote, due to &lt;a href=&quot;#postgresql-version-upgrade&quot;&gt;PostgreSQL&#x27;s upgrade&lt;&#x2F;a&gt; happening with GitLab
9.0, GitLab Geo 8.x is not compatible with GitLab Geo 9.0 and requires a
manual update. If you are an existing Geo user, please read the
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;geo&#x2F;replication&#x2F;updating_the_geo_nodes.html&quot;&gt;upgrade instructions&lt;&#x2F;a&gt;
before upgrading to GitLab 9.0.&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section text-center zero-bottom-margin&quot;&gt;
  &lt;h2 id=&quot;other-improvements-in-gitlab-90&quot;&gt;Other Improvements in GitLab 9.0&lt;&#x2F;h2&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-row align-top divider&quot;&gt;
  &lt;div class=&quot;column&quot;&gt;
    &lt;h3 id=&quot;native-unicode-emoji--ce-ees-eep&quot;&gt;Native Unicode Emoji 🔥 ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Unicode emojis allow for a more consistent feel with the rest of your OS and equates to you being able to add emojis faster 🚀. We were able to get rid some of the hefty images and JSON payloads and generate the awards emoji menu immediately instead of having a loading spinner to wait for an async response. 👯 ✨ 🏋 👌&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;award_emojis.html&quot;&gt;Learn more about award emojis in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;native_unicode_emojis.gif&quot; alt=&quot;Native unicode emojis&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;gitlab-ci-ce-ees-eep&quot;&gt;GitLab CI ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;To follow conventions of naming across GitLab, and to further move away from the
&lt;code&gt;build&lt;&#x2F;code&gt; term and toward &lt;code&gt;job&lt;&#x2F;code&gt;, CI variables &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9756&quot;&gt;have been renamed&lt;&#x2F;a&gt; for the 9.0
release.&lt;&#x2F;p&gt;

    &lt;table&gt;
      &lt;thead&gt;
        &lt;tr&gt;
          &lt;th&gt;8.X name&lt;&#x2F;th&gt;
          &lt;th&gt;9.0 name&lt;&#x2F;th&gt;
        &lt;&#x2F;tr&gt;
      &lt;&#x2F;thead&gt;
      &lt;tbody&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_ID&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_JOB_ID&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_REF&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_COMMIT_SHA&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_TAG&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_COMMIT_TAG&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_REF_NAME&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_COMMIT_REF_NAME&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_REF_SLUG&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_COMMIT_REF_SLUG&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_NAME&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_JOB_NAME&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_STAGE&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_JOB_STAGE&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_REPO&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_REPOSITORY_URL&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_TRIGGERED&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_PIPELINE_TRIGGERED&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_MANUAL&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_JOB_MANUAL&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
        &lt;tr&gt;
          &lt;td&gt;&lt;code&gt;CI_BUILD_TOKEN&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
          &lt;td&gt;&lt;code&gt;CI_JOB_TOKEN&lt;&#x2F;code&gt;&lt;&#x2F;td&gt;
        &lt;&#x2F;tr&gt;
      &lt;&#x2F;tbody&gt;
    &lt;&#x2F;table&gt;

    &lt;p&gt;The old variables continue to work, however they are deprecated and will be removed soon.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;variables&#x2F;&quot;&gt;Read more about the CI variables in our documentation&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;gitaly-ce-ees-eep&quot;&gt;Gitaly ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;In every release, GitLab becomes faster with huge performance boosts. Today&#x27;s
release is no different. Along with &lt;a href=&quot;#performance-improvements-ce-ee&quot;&gt;other performance improvements&lt;&#x2F;a&gt;,
GitLab now ships with &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitaly&quot;&gt;Gitaly&lt;&#x2F;a&gt;, our own
open-source solution to handle git calls made by GitLab. While completely
transparent, this change in how GitLab operates internally is important and
will make GitLab faster. We are actively working on Gitaly, so you can expect
more news about it in future releases.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;group-search-and-filtering-ce-ees-eep&quot;&gt;Group search and filtering ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;With our new version of groups in 9.0, we anticipate you&#x27;ll create much more of them. So we&#x27;ve made it possible to filter and search groups in the list view, and also allow you to sort by when they were created or updated.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;filter_groups.png&quot; alt=&quot;Filter Groups&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;tokenized-filter-and-search-in-issues-and-merge-requests-ce-ees-eep&quot;&gt;Tokenized Filter and Search in Issues and Merge Requests ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;We first introduced the new streamlined filter and search interface for issues in &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;01&#x2F;22&#x2F;gitlab-8-16-released&#x2F;&quot;&gt;8.16&lt;&#x2F;a&gt;. With 9.0, we are tokenizing the filter attributes for even more visual clarity. Many other places in GitLab deserve this new interface. We&#x27;re bringing it to merge requests in 9.0, and will roll it out to other parts of GitLab in future releases.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;mr_new_search_interface.png&quot; alt=&quot;Merge Requests New Search Interface&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;impersonation-tokens-ce-ees-eep&quot;&gt;Impersonation Tokens ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Alongside the new API, we&#x27;ve also added &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;issues&#x2F;25367&quot;&gt;Impersonation tokens&lt;&#x2F;a&gt;. If you&#x27;ve ever built a bot or a piece of functionality with our API, you&#x27;ll often have to retrieve a token via OAuth. This can sometimes be undesirable and cumbersome to have to go through a UI flow in order to retrieve this token. Administrators of a GitLab instance can now retrieve an impersonation token on behalf of a user to make this process a lot easier and centrally controlled. This process will also alleviate any issues caused by users inadvertently invalidating tokens in use for other applications.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;index.html#impersonation-tokens&quot;&gt;Read more about impersonation tokens in our API docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;gitlab-pages-artifacts-cleaned-after-deployment-ce-ees-eep&quot;&gt;GitLab Pages artifacts cleaned after deployment ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;In order to more efficiently utilize artifact storage space, &lt;a href=&quot;https:&#x2F;&#x2F;pages.gitlab.io&#x2F;&quot;&gt;GitLab Pages&lt;&#x2F;a&gt; artifacts are now automatically deleted after they have been deployed. If you would like to retain artifacts, an &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;yaml&#x2F;#artifacts-expire_in&quot;&gt;expiry duration&lt;&#x2F;a&gt; can be set.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;comments-in-diffs-ce-ees-eep&quot;&gt;Comments in diffs ce ees eep&lt;&#x2F;h3&gt;
    &lt;p&gt;Commenting in diffs is now much easier with a purple background indicating which line we are selecting.
Going through discussion in comments is also much easier now that we can collapse discussions and
see note authors avatars in the sidebar of the diff.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;diff_comments.gif&quot; alt=&quot;Comments in diffs&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;pipeline-triggers-with-user-permissions-ce-ees-eep&quot;&gt;Pipeline triggers with User permissions ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;A new &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;pipeline_triggers.html&quot;&gt;Pipeline Trigger API&lt;&#x2F;a&gt; and UI is now available, which utilize the user level permissions of their creator. This enables the token to be used not just for the current project, but also all dependent projects as well. The Build Trigger API remains functional, however it is deprecated and will be removed soon.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;new-default-value-for-ci-variable-cachekey-ce-ees-eep&quot;&gt;New default value for CI variable &quot;cache:key&quot; ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Unless specifically configured, the value of &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;yaml&#x2F;#cachekey&quot;&gt;&lt;code&gt;cache:key&lt;&#x2F;code&gt;&lt;&#x2F;a&gt; is now &lt;code&gt;default&lt;&#x2F;code&gt;. This allows the cache to be shared between all pipelines and jobs within the project, increasing CI&#x2F;CD efficiency and speed.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;blocking-manual-actions-in-pipelines-ce-ees-eep&quot;&gt;Blocking manual actions in pipelines ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;ci&#x2F;jobs&#x2F;job_control.html#create-a-job-that-must-be-run-manually&quot;&gt;Manual actions&lt;&#x2F;a&gt; can now be configured to block pipelines until they are completed. Pipelines blocked by manual actions have a status of &lt;code&gt;manual&lt;&#x2F;code&gt;, and can be enabled by setting &lt;code&gt;allow_failure&lt;&#x2F;code&gt; to &lt;code&gt;false&lt;&#x2F;code&gt;.&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;more-control-over-http-strict-transport-security-ce-ees-eep&quot;&gt;More control over HTTP Strict Transport Security ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Now you fine tune your Strict Transport Security enforcement just by changing settings in your Omnibus GitLab config.
Use HTTP Strict Transport Security to provide your installation with even better protection against MITM attacks.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;settings&#x2F;nginx.html#setting-http-strict-transport-security&quot;&gt;Learn more about HSTS in Omnibus in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

  &lt;&#x2F;div&gt;
  &lt;div class=&quot;column&quot;&gt;

    &lt;h3 id=&quot;new-branch-for-bare-projects-ce-ees-eep&quot;&gt;New Branch for Bare Projects ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;When you click the &lt;code&gt;New branch&lt;&#x2F;code&gt; button in an issue, you may want to start creating code right away.
But for a project with an empty repository, GitLab, prior to 9.0, stubbornly sends you back to the main project view when you click the button.
With 9.0, when you do click the &lt;code&gt;New branch&lt;&#x2F;code&gt; in an empty repository project, GitLab automatically creates the master branch, commits a blank &lt;code&gt;README.md&lt;&#x2F;code&gt; file to it, and creates and redirects you to a new branch based on the issue title.
If your &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;integrations&#x2F;project_services.html&quot;&gt;project is already configured with a deployment service&lt;&#x2F;a&gt; (e.g. Kubernetes), GitLab takes one step further and prompts you to set up &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;autodevops&#x2F;stages.html&quot;&gt;auto deploy&lt;&#x2F;a&gt; by helping you create a &lt;code&gt;.gitlab-ci.yml&lt;&#x2F;code&gt; file.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;user&#x2F;project&#x2F;repository&#x2F;web_editor.html#create-a-new-branch-from-an-issue&quot;&gt;Read more about creating new branches from issues in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;no_repo_new_branch.png&quot; alt=&quot;New Branch for Repo-less Projects in GitLab 9.0&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;merge-request-widget-usability-ce-ees-eep&quot;&gt;Merge Request Widget Usability ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;The merge request plays a crucial role in code collaboration and deployment. In particular, a lot of important information and call-to-actions are located in the merge request widget. With 9.0, we are starting to improve the usability of that widget. We want to present the most relevant information and allow you to see, at a glance, the status of the code, whether it&#x27;s in review, or if it&#x27;s already deployed in an environment. We will continue to iterate on this new cleaner design, and continue to make the entire merge request more powerful.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;merge_request_widget.png&quot; alt=&quot;Merge Request Widget&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;create-mattermost-team-when-creating-gitlab-group-ce-ees-eep&quot;&gt;Create Mattermost Team when Creating GitLab Group ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Sometimes chatting with your workgroup is the best way to get an idea rolling. To help you with that, GitLab integrates with &lt;a href=&quot;https:&#x2F;&#x2F;about.mattermost.com&#x2F;&quot;&gt;Mattermost&lt;&#x2F;a&gt;. With GitLab 9.0, setting up a &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;gitlab-mattermost&#x2F;README.html#gitlab-mattermost&quot;&gt;Mattermost team&lt;&#x2F;a&gt; for your GitLab group to chat and collaborate is effortless. When creating a GitLab group, select the appropriate checkbox, and GitLab will tell your Mattermost instance to create a team with the same name.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;group-creation-mm.png&quot; alt=&quot;Create GitLab Group Create Mattermost Team&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;paginated-environments-ce-ees-eep&quot;&gt;Paginated environments ce ees eep&lt;&#x2F;h3&gt;

    &lt;p&gt;Pagination was added to environments list in order to improve performance and user experience.
Environments that belong to a folder are now shown in a new view.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;environments_pagination.png&quot; alt=&quot;Root Level Environments&quot; class=&quot;shadow&quot; &#x2F;&gt;
&lt;img src=&quot;&#x2F;images&#x2F;9_0&#x2F;environments_folder_view.png&quot; alt=&quot;Environments inside a folder&quot; class=&quot;shadow&quot; &#x2F;&gt;&lt;&#x2F;p&gt;

    &lt;h3 id=&quot;notable-community-contributions-ce&quot;&gt;Notable Community Contributions ce&lt;&#x2F;h3&gt;

    &lt;ul&gt;
      &lt;li&gt;Add the Username to the HTTP(S) clone URL of a Repository (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9347&quot;&gt;!9347&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;API: Make it possible to pass coverage value to commit status endpoint (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9214&quot;&gt;!9214&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Show directory hierarchy when listing wiki pages (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8133&quot;&gt;!8133&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add a feature to create a &#x27;directly addressed&#x27; Todo when mentioned in the beginning of a line (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;7926&quot;&gt;!7926&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Todos can now be undone (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8691&quot;&gt;!8691&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Show 99+ for large count in todos notification bell (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9171&quot;&gt;!9171&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add the option to filter todos by Added (Marked) and Pipelines (Build failed) (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8861&quot;&gt;!8861&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add merge request count to each issue on issues list (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9252&quot;&gt;!9252&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Introduce &lt;code&gt;&#x2F;award&lt;&#x2F;code&gt; slash command; Allow posting of just an emoji in comment (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9382&quot;&gt;!9382&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add a button to create an issue for a failing build (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9391&quot;&gt;!9391&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add user &amp;amp; build links in Slack Notifications (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;8641&quot;&gt;!8641&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Add the ability to copy a branch name to the clipboard (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9103&quot;&gt;!9103&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
      &lt;li&gt;Brand header logo for pipeline emails (&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;merge_requests&#x2F;9049&quot;&gt;!9049&lt;&#x2F;a&gt;)&lt;&#x2F;li&gt;
    &lt;&#x2F;ul&gt;

    &lt;h3 id=&quot;omnibus-gitlab-package-improvements-ce-ees-eep&quot;&gt;Omnibus GitLab Package Improvements ce ees eep&lt;&#x2F;h3&gt;

    &lt;h4 id=&quot;postgresql-version-upgrade&quot;&gt;PostgreSQL version upgrade&lt;&#x2F;h4&gt;

    &lt;p&gt;Previous GitLab releases were shipped with PostgreSQL 9.2 by default. PostgreSQL
9.2&#x27;s end of life (EOL) is &lt;a href=&quot;https:&#x2F;&#x2F;www.postgresql.org&#x2F;support&#x2F;versioning&#x2F;&quot;&gt;set to September 2017&lt;&#x2F;a&gt;.
For this reason, as well as to have the latest features and performance
improvements, we need to update the PostgreSQL version that GitLab uses.&lt;&#x2F;p&gt;

    &lt;p&gt;GitLab 9.0 now ships with PostgreSQL 9.6 by default. For existing installations,
the omnibus-gitlab packages for GitLab 9.0 will attempt to automatically upgrade
your database, using the &lt;code&gt;gitlab-ctl pg-upgrade&lt;&#x2F;code&gt; tool that is included
&lt;a href=&quot;&#x2F;releases&#x2F;2016&#x2F;12&#x2F;22&#x2F;gitlab-8-15-released&#x2F;#postgresql-version-upgrade&quot;&gt;since 8.15&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;settings&#x2F;database.html#upgrade-packaged-postgresql-server&quot;&gt;Read more about database upgrade in our docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;p&gt;Ran into issues? Create an issue at the &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&quot;&gt;omnibus-gitlab issue tracker&lt;&#x2F;a&gt;,
and reference it in the &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;1783&quot;&gt;upgrade problems meta issue.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

    &lt;h4 id=&quot;gitlab-mattermost-37&quot;&gt;GitLab Mattermost 3.7&lt;&#x2F;h4&gt;

    &lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;about.mattermost.com&#x2F;mattermost-3-7&quot;&gt;Mattermost 3.7&lt;&#x2F;a&gt; is included in
GitLab 9.0. The &lt;a href=&quot;https:&#x2F;&#x2F;about.mattermost.com&#x2F;&quot;&gt;open source Slack-alternative&#x27;s&lt;&#x2F;a&gt;
newest release offers group messaging for quick, direct chats, custom channel push
notification preferences, new website link previews and much more.&lt;&#x2F;p&gt;

    &lt;p&gt;This version includes &lt;a href=&quot;http:&#x2F;&#x2F;about.mattermost.com&#x2F;security-updates&#x2F;&quot;&gt;security updates&lt;&#x2F;a&gt;
and upgrade is recommended.&lt;&#x2F;p&gt;

    &lt;h4 id=&quot;raspberry-pi-2-changes&quot;&gt;Raspberry Pi 2 changes&lt;&#x2F;h4&gt;

    &lt;p&gt;Due to a fault in release process that was caused by changes in build infrastructure,
packages for Raspberry Pi 2 &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;omnibus-gitlab&#x2F;issues&#x2F;1303&quot;&gt;were tagged under Debian distribution instead of Raspbian&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;p&gt;We&#x27;ve resolved this issue and also synced all latest versions of packages
to &lt;code&gt;Raspbian&lt;&#x2F;code&gt; distribution.&lt;&#x2F;p&gt;

    &lt;p&gt;Going forward, we will only release Raspberry Pi 2 packages under &lt;code&gt;Raspbian&lt;&#x2F;code&gt; distribution.
Further more, as &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;02&#x2F;22&#x2F;gitlab-8-17-released&#x2F;#raspbian-wheezy-package&quot;&gt;announced in 8.17 release post&lt;&#x2F;a&gt;,
we will provide only Jessie packages for Raspberry Pi 2.&lt;&#x2F;p&gt;

    &lt;p&gt;If you did any manual changes to the apt repository as a workaround, you will need to change the distribution.
You can do this by running:&lt;&#x2F;p&gt;

&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight plaintext&quot;&gt;&lt;code&gt;sed -i &#x27;s&#x2F;debian&#x2F;raspbian&#x2F;g&#x27; &#x2F;etc&#x2F;apt&#x2F;sources.list.d&#x2F;gitlab_raspberry-pi2.list
&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;&lt;&#x2F;div&gt;
    &lt;h4 id=&quot;monitoring-gitlab-with-prometheus&quot;&gt;Monitoring GitLab with Prometheus&lt;&#x2F;h4&gt;

    &lt;p&gt;With the release of GitLab 9.0, Prometheus and its associated exporters are now on by default. It is now easier than ever to ensure your GitLab service is healthy and responsive, with over 100 metrics available for monitoring. If you would like to disable Prometheus and all of it&#x27;s related services, simply set:&lt;&#x2F;p&gt;

&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight plaintext&quot;&gt;&lt;code&gt;prometheus_monitoring[&#x27;enable&#x27;] = false
&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;&lt;&#x2F;div&gt;
    &lt;p&gt;&lt;i class=&quot;fas fa-book&quot; aria-hidden=&quot;true&quot;&gt;&lt;&#x2F;i&gt;
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;monitoring&#x2F;prometheus&#x2F;&quot;&gt;Read more on monitoring with Prometheus docs&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;

  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 class=&quot;text-center&quot; id=&quot;deprecations&quot;&gt;Deprecations&lt;&#x2F;h2&gt;

  &lt;h3 id=&quot;gitlab-runner-deprecation&quot;&gt;GitLab Runner Deprecation&lt;&#x2F;h3&gt;

  &lt;p&gt;Please note that GitLab Runners prior to 9.0 utilize API v3, and therefore are deprecated along with the v3 API. Runners version 9.0 and above utilize the &lt;a href=&quot;#api-v4-ce-ee&quot;&gt;new v4 API&lt;&#x2F;a&gt;, requiring a minimum of GitLab 9.0.&lt;&#x2F;p&gt;

  &lt;p&gt;Due: &lt;strong&gt;August 2017&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;git-annex-deprecation&quot;&gt;Git-Annex deprecation&lt;&#x2F;h3&gt;

  &lt;p&gt;As &lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;02&#x2F;22&#x2F;gitlab-8-17-released&#x2F;#git-annex-support&quot;&gt;previously announced&lt;&#x2F;a&gt;,
support for &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;git_annex.html&quot;&gt;Git-Annex&lt;&#x2F;a&gt; has
been deprecated in GitLab 9.0.&lt;&#x2F;p&gt;

  &lt;p&gt;Read through the
&lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;topics&#x2F;git&#x2F;lfs&#x2F;migrate_from_git_annex_to_git_lfs.html&quot;&gt;Git-Annex to Git-LFS migration guide&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;Due: &lt;strong&gt;today&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;

  &lt;h3 id=&quot;gitlab-pages-ip-on-gitlabcom&quot;&gt;GitLab Pages IP on GitLab.com&lt;&#x2F;h3&gt;

  &lt;p&gt;We&#x27;ve changed the &lt;strong&gt;IP address&lt;&#x2F;strong&gt; of GitLab Pages server on &lt;strong&gt;GitLab.com&lt;&#x2F;strong&gt;. Your DNS &lt;code&gt;A&lt;&#x2F;code&gt; record needs update.
For more info, please read the blog post &quot;&lt;a href=&quot;&#x2F;releases&#x2F;2017&#x2F;03&#x2F;06&#x2F;we-are-changing-the-ip-of-gitlab-pages-on-gitlab-com&#x2F;&quot;&gt;We are changing the IP of GitLab Pages on GitLab.com&lt;&#x2F;a&gt;&quot;.&lt;&#x2F;p&gt;

  &lt;p&gt;Due: &lt;strong&gt;March 31st&lt;&#x2F;strong&gt;, 2017 at 23:59h UTC.&lt;&#x2F;p&gt;

&lt;&#x2F;section&gt;
&lt;!-- END OF DEPRECATIONS BLOCK --&gt;

&lt;!-- UPGRADE BAROMETER BLOCK --&gt;
&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;h2 class=&quot;text-center&quot; id=&quot;upgrade-barometer&quot;&gt;Upgrade barometer&lt;&#x2F;h2&gt;

  &lt;p&gt;To upgrade to GitLab 9.0, downtime is required. Larger instances (&amp;gt;1000 users)
should expect about 15 minutes of downtime.&lt;&#x2F;p&gt;

  &lt;p&gt;The specific migrations requiring downtime or taking significant time are described below.&lt;&#x2F;p&gt;
  &lt;ul&gt;
    &lt;li&gt;Some columns are renamed. This operation requires downtime.&lt;&#x2F;li&gt;
    &lt;li&gt;A new column is added to users table, which does not require downtime but may take some time to complete.&lt;&#x2F;li&gt;
    &lt;li&gt;The builds table is updated, which does not require downtime but may take some time depending on your CI usage.&lt;&#x2F;li&gt;
  &lt;&#x2F;ul&gt;

  &lt;p&gt;GitLab 9.0 introduces a &lt;a href=&quot;#api-v4&quot;&gt;new version of our API&lt;&#x2F;a&gt;. While existing calls
to API v3 will continue to work until August 2017, we advise you to make any
necessary changes to applications that use the v3 API. &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;api&#x2F;v3_to_v4.html&quot;&gt;Read the documentation&lt;&#x2F;a&gt;
to learn more.&lt;&#x2F;p&gt;

  &lt;p&gt;Because of PostgreSQL&#x27;s upgrade, GitLab 9.0 introduces a breaking change to
GitLab Geo. If you are an existing Geo user, please refer to the &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;ee&#x2F;administration&#x2F;geo&#x2F;replication&#x2F;updating_the_geo_nodes.html&quot;&gt;documentation
before upgrading to 9.0&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;h4 id=&quot;note&quot;&gt;Note&lt;&#x2F;h4&gt;

  &lt;p&gt;We assume you are upgrading from the latest version. If not, then also consult the upgrade barometers of any intermediate versions you are skipping.
If you are upgrading from a GitLab version prior to 8.0 &lt;em&gt;and&lt;&#x2F;em&gt; you have CI enabled, you have to upgrade to GitLab 8.0 &lt;a href=&quot;&#x2F;releases&#x2F;2015&#x2F;09&#x2F;22&#x2F;gitlab-8-0-released&#x2F;&quot;&gt;first&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;New configuration options have been introduced in the omnibus-gitlab packages. To
check what changed compared to your &lt;code&gt;&#x2F;etc&#x2F;gitlab&#x2F;gitlab.rb&lt;&#x2F;code&gt; configuration
file, run &lt;code&gt;sudo gitlab-ctl diff-config&lt;&#x2F;code&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;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 &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitlab.com&#x2F;omnibus&#x2F;update&#x2F;README.html&quot;&gt;&lt;code&gt;&#x2F;etc&#x2F;gitlab&#x2F;skip-auto-migrations&lt;&#x2F;code&gt;
file&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

  &lt;p&gt;If you&#x27;re GitLab EE user, please be aware that in 9.0 release we bumped the required version of Elasticsearch from 2.4.x to 5.1.x.
Please update it following the official &lt;a href=&quot;https:&#x2F;&#x2F;www.elastic.co&#x2F;guide&#x2F;en&#x2F;elasticsearch&#x2F;reference&#x2F;5.1&#x2F;setup-upgrade.html&quot;&gt;documentation&lt;&#x2F;a&gt;.
Indexes created by Elasticsearch 2.4.x can be read by Elasticsearch 5.1.x.&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;
&lt;!-- END OF UPGRADE BAROMETER BLOCK --&gt;

&lt;section class=&quot;gray-section&quot;&gt;
  &lt;div class=&quot;release-row align-top&quot;&gt;
    &lt;div class=&quot;column&quot;&gt;
      &lt;h3 id=&quot;changelog&quot;&gt;Changelog&lt;&#x2F;h3&gt;

      &lt;p&gt;Please check out the changelog to see all the named changes:&lt;&#x2F;p&gt;

      &lt;ul&gt;
        &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&#x2F;blob&#x2F;master&#x2F;CHANGELOG.md&quot;&gt;GitLab CE&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
        &lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;blob&#x2F;master&#x2F;CHANGELOG.md&quot;&gt;GitLab EE&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
      &lt;&#x2F;ul&gt;

      &lt;h3 id=&quot;installing&quot;&gt;Installing&lt;&#x2F;h3&gt;

      &lt;p&gt;If you are setting up a new GitLab installation please see the
&lt;a href=&quot;&#x2F;install&#x2F;&quot;&gt;download GitLab page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

      &lt;h3 id=&quot;updating&quot;&gt;Updating&lt;&#x2F;h3&gt;

      &lt;p&gt;Check out our &lt;a href=&quot;&#x2F;update&#x2F;&quot;&gt;update page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;

    &lt;&#x2F;div&gt;
    &lt;div class=&quot;column&quot;&gt;

      &lt;h3 id=&quot;gitlab-products&quot;&gt;GitLab Products&lt;&#x2F;h3&gt;

      &lt;p&gt;We offer four different &lt;a href=&quot;&#x2F;stages-devops-lifecycle&#x2F;&quot;&gt;products&lt;&#x2F;a&gt; for you and your company:&lt;&#x2F;p&gt;

      &lt;ul&gt;
        &lt;li id=&quot;ce&quot;&gt;&lt;strong&gt;GitLab Community Edition (CE)&lt;&#x2F;strong&gt;: &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ce&quot;&gt;Open source&lt;&#x2F;a&gt;, self-managed solution of GitLab. Ideal for personal projects or small teams with minimal user management and workflow control needs. Every feature available in GitLab CE, is also available on GitLab Enterprise Edition (Starter and Premium), and GitLab.com.&lt;&#x2F;li&gt;
        &lt;li id=&quot;ee&quot;&gt;&lt;strong&gt;&lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;GitLab Enterprise Edition&lt;&#x2F;a&gt; (EE)&lt;&#x2F;strong&gt;: &lt;a href=&quot;https:&#x2F;&#x2F;gitlab.com&#x2F;gitlab-org&#x2F;gitlab-ee&#x2F;&quot;&gt;Open core&lt;&#x2F;a&gt;, self-managed, fully featured solution of GitLab. Available in two different subscriptions:
          &lt;ul&gt;
            &lt;li id=&quot;ees&quot;&gt;&lt;strong&gt;GitLab Enterprise Edition Starter (EES)&lt;&#x2F;strong&gt;: Ideal for co-located teams who need additional security and workflow controls for their professional projects.&lt;&#x2F;li&gt;
            &lt;li id=&quot;eep&quot;&gt;&lt;strong&gt;GitLab Enterprise Edition Premium (EEP)&lt;&#x2F;strong&gt;: Ideal for distributed teams who need advanced workflow controls, premium features, High Availability, and Premium Support.&lt;&#x2F;li&gt;
          &lt;&#x2F;ul&gt;
        &lt;&#x2F;li&gt;
        &lt;li id=&quot;gitlab-dot-com&quot;&gt;**&lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;GitLab.com&lt;&#x2F;a&gt; **: Free GitLab solution, which runs on top of GitLab EES, hosted by GitLab, Inc. Ideal for individuals who want to get their projects up and running quickly. Administrated by GitLab (users don&#x27;t have access to admin settings).&lt;&#x2F;li&gt;
      &lt;&#x2F;ul&gt;

    &lt;&#x2F;div&gt;
  &lt;&#x2F;div&gt;
&lt;&#x2F;section&gt;

&lt;section class=&quot;release-post-section&quot;&gt;
  &lt;p class=&quot;note text-center&quot;&gt;&lt;a href=&quot;https:&#x2F;&#x2F;www.pexels.com&#x2F;photo&#x2F;landscape-nature-mountain-lake-37650&#x2F;&quot;&gt;Cover image&lt;&#x2F;a&gt; licensed under &lt;a href=&quot;https:&#x2F;&#x2F;www.pexels.com&#x2F;photo-license&#x2F;&quot;&gt;CC0&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;&#x2F;section&gt;

&lt;style&gt;
  .badge-container a {
    margin-right: 3px;
  }
&lt;&#x2F;style&gt;

&lt;img src=&#x27;https:&#x2F;&#x2F;about.gitlab.com&#x2F;images&#x2F;9_0&#x2F;9_0-cover-image.jpeg&#x27; class=&#x27;webfeedsFeaturedVisual&#x27; style=&#x27;display: none;&#x27; &#x2F;&gt;</content>
</entry>
</feed>