about.gitlab.com Open in urlscan Pro
2a04:4e42:600::561  Public Scan

Form analysis
3 forms found in the DOM

<form id="mktoForm_1077" novalidate="novalidate" class="mktoForm mktoHasWidth mktoLayoutLeft" data-styles-ready="true">
  <style type="text/css"></style>
  <div class="mktoFormRow">
    <div class="mktoFieldDescriptor mktoFormCol">
      <div class="mktoOffset"></div>
      <div class="mktoFieldWrap mktoRequiredField"><label for="Email" id="LblEmail" class="mktoLabel mktoHasWidth">
          <div class="mktoAsterix">*</div>Enter your email address
        </label>
        <div class="mktoGutter mktoHasWidth"></div><input id="Email" name="Email" placeholder="abc@xyz.com" maxlength="255" aria-labelledby="LblEmail InstructEmail" type="email" class="mktoField mktoEmailField mktoHasWidth mktoRequired"
          aria-required="true"><span id="InstructEmail" tabindex="-1" class="mktoInstruction"></span>
        <div class="mktoClear"></div>
      </div>
      <div class="mktoClear"></div>
    </div>
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow">
    <div class="mktoFormCol">
      <div class="mktoOffset mktoHasWidth"></div>
      <div class="mktoFieldWrap">
        <div class="mktoHtmlText mktoHasWidth">By subscribing to this newsletter, I consent to GitLab sending me monthly blog emails in accordance with <a href="https://about.gitlab.com/privacy/" target="_blank" id="">GitLab's Privacy Statement</a>.
          I may opt-out at anytime by clicking "unsubscribe" in the email footer or by visiting our <a href="https://about.gitlab.com/company/preference-center/" target="_blank" id="">Communications Preference Center</a>.</div>
        <div class="mktoClear"></div>
      </div>
      <div class="mktoClear"></div>
    </div>
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="gclid" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="GACLIENTID__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="GATRACKID__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="demandbase_sid__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_Name__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_Address__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_City__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_State__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_Postal__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_Country__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Company_Phone__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Employee_Count__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Audience__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Industry__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_SubIndustry__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Primary_SIC__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Watch_List_Account_Owner__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Watch_List_Account_Type__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Watch_List_Campaign_Code__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="DB_Website__c" class="mktoField mktoFieldDescriptor mktoFormCol" value="">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoFormRow"><input type="hidden" name="newsletterSegment__c_lead" class="mktoField mktoFieldDescriptor mktoFormCol" value="Yes">
    <div class="mktoClear"></div>
  </div>
  <div class="mktoButtonRow"><span class="mktoButtonWrap mktoNative"><button type="submit" class="mktoButton">Subscribe</button></span></div><input type="hidden" name="formid" class="mktoField mktoFieldDescriptor" value="1077"><input type="hidden"
    name="munchkinId" class="mktoField mktoFieldDescriptor" value="194-VVC-221">
</form>

<form>
  <input class="st-default-search-input st-search-set-focus" type="text" value="" placeholder="Search this site" aria-label="Search this site" id="st-overlay-search-input" autocomplete="off" autocorrect="off" autocapitalize="off">
</form>

<form novalidate="novalidate" class="mktoForm mktoHasWidth mktoLayoutLeft" style="font-family: inherit; font-size: 13px; color: rgb(51, 51, 51); visibility: hidden; position: absolute; top: -500px; left: -1000px; width: 1600px;"></form>

Text Content

Apr 22, 2023 - Melissa Ushakov   Melissa Ushakov


GITLAB 15.11 RELEASE


GITLAB 15.11 RELEASED WITH CODE SUGGESTIONS

GitLab 15.11 released with Code Suggestions, project compliance frameworks
report management at the group level, re-running downstream pipeline trigger
jobs, vulnerability dismissal reasons, and much more!

Today, we are excited to announce the release of GitLab 15.11 with Code
Suggestions, project compliance frameworks report management at the group level,
re-running downstream pipeline trigger jobs, vulnerability dismissal reasons,
and much more!

These are just a few highlights from the 110+ improvements in this release. Read
on to check out all of the great updates below.

We thank the wider GitLab community for the 180 contributions they provided to
GitLab 15.11! At GitLab, everyone can contribute and we couldn't have done it
without you!

To preview what's coming in next month’s release, check out our Upcoming
Releases page, which includes our 16.0 release kickoff video.

GitLab 15.11 released with Code Suggestions Click to tweet!


MVP THIS MONTH'S MOST VALUABLE PERSON (MVP) IS WEYERT DE BOER

Weyert added dependency scanning support for pnpm (JavaScript package manager).
Thanks to Weyert’s contributions, multiple customers who requested this feature
can now identify security vulnerabilities in pnpm lockfiles!

“Weyert’s patience, thoroughness, attention to detail, and motivation were
instrumental in completing this challenging piece of work. Weyert quickly
responded to code review feedback, provided detailed and clear explanations for
implementation decisions, created follow-up documentation merge requests, and
even diagnosed and fixed a bug before the feature was made generally available!
Well done Weyert for having the persistence and dedication to see this important
feature through to completion!” said Adam Cohen, Sr. Backend Engineer at GitLab.

Weyert works at Tapico as a lead engineer and maintains the Tapico Marketplace
for financial apps. He is excited that Gitlab, through his contribution, now
supports pnpm and hopes to start using it at work soon.

Thank you Weyert! 🙌


15.11 KEY IMPROVEMENTS RELEASED IN GITLAB 15.11

CODE SUGGESTIONS FOR ULTIMATE & PREMIUM USERS

CODE SUGGESTIONS FOR ULTIMATE & PREMIUM USERS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Every day, millions of developers use GitLab to contribute code. In February, we
launched a closed Beta of this feature, and since then, we’ve been working hard
to make Code Suggestions available to more developers. During Beta, Code
Suggestions is free for all Ultimate and Premium customers. Group admins can
enable this setting with a new group-level control. Depending on the prompt, the
extension either provides entire code snippets, like generating functions, or
completes the current line. To accept the suggestions, simply press Tab.

GitLab Code Suggestions can improve developer productivity, focus, and
innovation without context switching and within a single DevSecOps platform.
Please note that this is a high-demand Beta feature and may have unscheduled
downtime. During Beta, it may also produce low-quality or incomplete
suggestions. Read about known limitations. We are continuously iterating to
improve Code Suggestions and make it better. Give it a try, and share your
feedback with us.


Documentation Issue

WEB IDE BETA ENABLED BY DEFAULT ON SELF-MANAGED

WEB IDE BETA ENABLED BY DEFAULT ON SELF-MANAGED

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

The Web IDE Beta brings powerful new capabilities and dramatically improved
performance to the web-based code editor. The Web IDE Beta has been available
for self-managed instances since GitLab 15.7, but was disabled behind a feature
flag.

From GitLab 15.11, the Web IDE Beta is now the default editor for all
self-managed instances. You can opt out of the Web IDE Beta any time in your
user preferences.

Documentation Issue


AWARD ACHIEVEMENTS TO USERS

AWARD ACHIEVEMENTS TO USERS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Using achievements, users can now acknowledge the accomplishments of others and
reward the effort and skill that they have demonstrated. You can now receive
achievements for your contributions on GitLab, and display them on your user
profile. An achievement consists of a name, a description and an avatar. Users
with the Maintainer or Owner role can create custom achievements, award them to
users meeting the achievement criteria, and revoke them if they no longer meet
the criteria. Up to three of your most recent achievements will display
underneath your profile image on your user profile page. If you prefer not to
display achievements on your profile, you can opt out in the user profile
settings.

In 15.11, we are releasing a Beta of this capability behind a feature flag. If
you want to try it out on self-managed GitLab, ask your administrator to enable
it. For GitLab.com, please request access in the feedback issue 405153.

We hope that this change will increase productivity and engagement in
organizations, and motivate team members to showcase their skills and
accomplishments. Please share your experiences in issue 405153.

Documentation Issue


GOOGLE PLAY STORE INTEGRATION

GOOGLE PLAY STORE INTEGRATION

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

From GitLab 15.11, you can configure and validate your projects with Google Play
Store credentials. You can then use those credentials in CI/CD pipelines to
automate releases to the Google Play Store.

To record your experiences with the Google Play Store integration, see this
feedback issue.

Documentation Issue


MANAGE PROJECT COMPLIANCE FRAMEWORKS REPORT AT GROUP LEVEL

MANAGE PROJECT COMPLIANCE FRAMEWORKS REPORT AT GROUP LEVEL

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Prior to GitLab 15.11, if you wanted to add or remove a compliance framework
from a project, you needed to go to each project individually to manage which
framework was associated with the project. When managing more than a few
projects, this process was tedious and inefficient.

Now, you can manage which compliance frameworks are applied to your projects at
the group level, significantly reducing the amount of time needed to make sure
your projects are adhering to the regulations and standards you are measured
against.

In GitLab 15.10, you could view all the projects in your group and see which
ones had compliance frameworks applied to them. In GitLab 15.11, you can add or
remove compliance frameworks directly from the compliance frameworks report.

Documentation Issue


VULNERABILITY DISMISSAL REASONS

VULNERABILITY DISMISSAL REASONS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

In previous releases, you had to manually add a comment to specify why a
vulnerability was dismissed. In GitLab 15.11, you can add a reason for
dismissing a vulnerability to the Vulnerability Report. Now you can quickly and
consistently track why vulnerabilities were dismissed.

This feature is only available on GitLab.com. Support for self-managed instances
is tracked in this issue.

Documentation Epic


VALUE STREAMS DASHBOARD RELEASED IN BETA

VALUE STREAMS DASHBOARD RELEASED IN BETA

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

This new dashboard provides strategic insights into metrics that help decision
makers to identify trends and patterns to optimize software delivery. The Beta
release is focused on measuring software development (DORA4) and the flow of
value delivery (Value Stream Analytics) across projects and groups.

Organizations can use the Value Streams Dashboard to identify workflow
inefficiencies and opportunities for improvements by benchmarking key DevSecOps
metrics.

The Value Streams Dashboard offers visibility across every step of the software
development lifecycle, without needing to buy or maintain a third-party tool.

Documentation Issue


RERUN DOWNSTREAM PIPELINE TRIGGER JOBS

RERUN DOWNSTREAM PIPELINE TRIGGER JOBS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Previously, if you needed to trigger a rerun of an entire downstream pipeline,
you had to rerun the full upstream pipeline. This could be a time-consuming and
inefficient process, especially if the upstream pipeline has many jobs or other
downstream pipelines.

In this release, we’ve added the ability to rerun just the downstream pipeline,
without having to re-run the entire parent pipeline, by selecting Run again on
the trigger job. The newly triggered downstream pipeline replaces the original
downstream pipeline in the pipeline graph. This will save you time and resources
when you want just the downstream pipeline to run again.

Documentation Issue
Having trouble viewing this video? You may need to update your Cookie
Preferences to allow all cookies. You might also need to allow us on your
adblocker, firewall, or browser privacy settings.

DEFINE INPUTS FOR INCLUDED CI/CD CONFIGURATION

DEFINE INPUTS FOR INCLUDED CI/CD CONFIGURATION

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Previously, if you wanted to change the behavior of included CI/CD
configuration, like a CI/CD template, you may have used global CI/CD variables.
However, using global variables applies to the entire pipeline, not just the
included configuration, which was not always desirable.

This release adds the ability to declare mandatory or optional input parameters
for each includable configuration file. These input parameters replace the need
for global variables and are scoped to the included configuration only, having
no impact on the rest of the pipeline. This allows you to build more robust and
isolated CI/CD templates, as well as declare and enforce constraints. Learn how
to use CI interpolation in this example repo.

Documentation Issue



15.11 OTHER IMPROVEMENTS IN GITLAB 15.11

BETTER ERROR MESSAGE WHEN DIRECT TRANSFER SETTING IS DISABLED

BETTER ERROR MESSAGE WHEN DIRECT TRANSFER SETTING IS DISABLED

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

GitLab group and project migration by direct transfer requires that both GitLab
instances have the feature enabled in application settings by an instance
administrator. Until now, if you tried to initiate an import when the feature
was disabled on the source instance, you received a 404 error.

We’ve replaced the 404 error with an informative message, and provided guidance
on how to enable the feature.

Documentation Issue

IMPROVED DATA SYNC BETWEEN JIRA AND GITLAB FOR JIRA CLOUD APP

IMPROVED DATA SYNC BETWEEN JIRA AND GITLAB FOR JIRA CLOUD APP

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

In GitLab 15.11, we have improved syncing of both existing and new data between
Jira Cloud and the GitLab for Jira Cloud app.

Previously, when you added a namespace to the GitLab for Jira Cloud app, only
existing merge request data was synced to Jira. Now, existing branch and commit
data is also synced.

When you viewed a Jira issue, the GitLab for Jira Cloud app previously showed
related GitLab branches only if the branch name contained the Jira issue ID (for
example, my-branch-JIRA-1). The GitLab for Jira Cloud app now also links to
GitLab branches when you mention the Jira issue ID in the merge request title or
description.

Documentation Issue Issue

OPTION TO DISABLE LDAP SYNCHRONIZATION OF USER’S NAME

OPTION TO DISABLE LDAP SYNCHRONIZATION OF USER’S NAME

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

You can now configure LDAP synchronization to not include the user’s name.
Previously, LDAP synchronization always included this information, making it
impossible to change the name value in GitLab. This option is disabled by
default.

Documentation Issue

OPEN MODIFIED FILES IN THE WEB IDE BETA

OPEN MODIFIED FILES IN THE WEB IDE BETA

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

The Web IDE Beta allows you to review merge requests and make additional changes
to new and modified files without cloning the project to your local machine.
However, when launched from a merge request, the Web IDE Beta previously didn’t
open any of these files.

To make it easier to contribute, new and modified files now appear in separate
tabs when you open the Web IDE Beta from a merge request. Each file is presented
with inline diffs so you can review the changes immediately. To optimize
performance, the Web IDE Beta only opens the top 10 files (by number of lines
changed) in a merge request. In the file tree, any new or modified file is
indicated by an icon next to the filename.

Documentation Issue

DOCUMENTATION FOR USING THE AGENT FOR KUBERNETES WITH CUSTOM CERTIFICATES

DOCUMENTATION FOR USING THE AGENT FOR KUBERNETES WITH CUSTOM CERTIFICATES

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

GitLab 15.11 adds documentation to help you configure the agent for Kubernetes
when GitLab runs with a CI/CD integration and custom certificates. The
documentation includes steps to set up KAS and agentk, and to invoke kubectl
commands from GitLab CI/CD.

Documentation Issue

MULTIPLE APPROVAL RULES ARE AVAILABLE IN THE GITLAB UI

MULTIPLE APPROVAL RULES ARE AVAILABLE IN THE GITLAB UI

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

If you follow continuous delivery practices using GitLab approval rules,
previously you had to pick between Multiple approval rules and Unified approval
rules. Multiple approval rules are generally more flexible, but in past releases
were only available through the API. Approval rules settings pages now configure
multiple approval rules.

You can access your previously configure unified approval rule settings through
the GitLab API. We are looking into automatically migrating Unified approval
rules to Multiple approval rules. The migration cannot support all the use cases
and might be a breaking change for some users. For this reason, we recommend
migrating manually.

Documentation Issue

CONTAINER SCANNING OUTPUTS CYCLONEDX DOCUMENTS

CONTAINER SCANNING OUTPUTS CYCLONEDX DOCUMENTS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

To align with a popular Software Bill of Materials (SBOM) industry format
standard, the Container Scanning tool now outputs a CycloneDX SBOM for the
scanned image. This CycloneDX SBOM is named gl-sbom-report.cdx.json and is saved
in the same directory as the JSON report file. You can download CycloneDX SBOMs
the same way as other job artifacts.

Documentation Issue

STATIC ANALYSIS ANALYZER UPDATES

STATIC ANALYSIS ANALYZER UPDATES

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

GitLab Static Analysis includes many security analyzers that the GitLab Static
Analysis team actively manages, maintains, and updates. The following analyzer
updates were published during the 15.11 release milestone. These updates bring
additional coverage, bug fixes, and improvements.

 * CodeClimate analyzer updated to version 0.94.0. See CHANGELOG for further
   details.
 * Brakeman-based analyzer updated to version 5.4.1. See CHANGELOG for further
   details.
 * KICS-based analyzer updated to version 1.6.13. See CHANGELOG for further
   details.
 * KubeSec-based analyzer updated to version 2.13.0. See CHANGELOG for further
   details.
 * Secrets analyzer updated to version 8.16.2. See CHANGELOG for further
   details. We also added new rules:
   * Google Cloud OAuth client secrets.
   * GitLab feed tokens.
   * Digital Ocean tokens.
 * Security Code Scan-based analyzer updated to add support for .NET 7 by
   default. See CHANGELOG for further details.
 * Semgrep-based analyzer updated to version 1.17.1. We also fixed a parsing
   error related to Go false positive detection. See CHANGELOG for further
   details.
   * Thanks to @jnoordsij for this community contribution.
 * Sobelow-based analyzer updated to version 0.12.2. See CHANGELOG for further
   details.

If you include the GitLab-managed SAST template (SAST.gitlab-ci.yml), you don’t
need to do anything to receive these updates. However, if you override or
customize your own CI/CD template, you need to update your CI/CD configurations.

To remain on a specific version of any analyzer, you can pin to a minor version
of an analyzer. Pinning to a previous version prevents you from receiving
automatic analyzer updates and requires you to manually bump your analyzer
version in your CI/CD template.

For previous changes, see last month’s updates.

Documentation Issue

WARNINGS TO PREVENT ACCIDENTAL TOKEN LEAKS IN ISSUES, MRS, AND COMMENTS

WARNINGS TO PREVENT ACCIDENTAL TOKEN LEAKS IN ISSUES, MRS, AND COMMENTS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

When you create an issue, propose a merge request, or write a comment, you might
accidentally post a sensitive value. For example, you might paste in the details
of an API request or an environment variable that contains an authentication
token.

Now, GitLab checks if the text of your issue, merge request description,
comment, or reply contains a token. If a token is found, a warning message is
displayed. You can then edit your message before it’s sent to the server to be
posted.

This new protection is always on; you don’t have to set it up. Currently, it
checks for GitLab Personal Access Tokens (PATs) and Feed Tokens. Further
improvements are considered in issue 405147.

Documentation Issue

OMNIBUS IMPROVEMENTS

OMNIBUS IMPROVEMENTS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate
 * GitLab 15.11 includes Mattermost 7.9. This version includes security updates
   so you should upgrade from earlier versions.
 * In GitLab 16.0, the minimum supported version of PostgreSQL will become 13.
   Therefore, in 15.11 we will swap attempt_auto_pg_upgrade? to true. This
   function will attempt to automatically upgrade the version of PostgreSQL to
   13 in 15.11 in preparation for the new minimum PostgreSQL requirement in
   16.0. This is the same behavior we performed in preparation for the last
   minimum upgrade of PostgreSQL.

Documentation

DETAILED LINK PREVIEW VISIBLE FOR NON-PUBLICLY AVAILABLE PAGES

DETAILED LINK PREVIEW VISIBLE FOR NON-PUBLICLY AVAILABLE PAGES

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Previously, when a user selected a non-public GitLab link, the link preview did
not work due to the lack of OpenGraph and Twitter meta HTML tags for the sign-in
page. These tags have been added, and now the preview is visible when a user
selects a non-public GitLab link.

Thank you Anatoly Ubiyko for your contribution!

Documentation Issue

--------------------------------------------------------------------------------

MIGRATE GITLAB PROJECTS BY DIRECT TRANSFER USING API

MIGRATE GITLAB PROJECTS BY DIRECT TRANSFER USING API

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Until now you could migrate GitLab projects by direct transfer only when
migrating GitLab groups. If some projects failed to be migrated, you couldn’t
try to import only failed projects again. The workaround was to import chosen
projects by uploading export files, which imports only one project at a time.

With this release, you can migrate projects by direct transfer using the API.
You can use this to re-import only the chosen failed project. This also lays the
groundwork for this feature to be made available in the UI.

Documentation Issue

--------------------------------------------------------------------------------

NEW VISUALIZATION OF STAGES BREAKDOWN IN VALUE STREAM ANALYTICS

NEW VISUALIZATION OF STAGES BREAKDOWN IN VALUE STREAM ANALYTICS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

We updated the Value Stream Analytics overview and replaced the Total time line
chart with a stacked area chart. The new chart displays a breakdown of all
stages, with the time items spent in each stage over a selected time period.
This visualization simplifies the top-down optimization flow from the Value
Streams Dashboard to Value Stream Analytics, and helps you evaluate the progress
of each stage at a glance.

Documentation Issue

--------------------------------------------------------------------------------

IMPORT NUGET PACKAGES BY USING CI/CD PIPELINES

IMPORT NUGET PACKAGES BY USING CI/CD PIPELINES

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Have you been thinking about moving your NuGet registry to GitLab, but haven’t
been able to invest the time to plan the migration? GitLab is proud to announce
the MVC launch of a NuGet package importer. You can now use the Packages
Importer tool to import packages from any NuGet compliant registry, like
Artifactory.

To use the tool, simply create a config.yml file that contains the details of
the packages you want to import into GitLab. Then add the importer to a
.gitlab-ci.yml pipeline configuration file, and the importer does the rest. It
runs in the pipeline, dynamically generating a child pipeline with jobs that
import all the packages into your GitLab package registry.

Having trouble viewing this video? You may need to update your Cookie
Preferences to allow all cookies. You might also need to allow us on your
adblocker, firewall, or browser privacy settings.
Documentation Issue

--------------------------------------------------------------------------------

KUBERNETES 1.26 SUPPORT

KUBERNETES 1.26 SUPPORT

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

This release adds full support for Kubernetes version 1.26, released in December
2022. If you use Kubernetes, you can now upgrade your clusters to the most
recent version and take advantage of all its features.

You can read more about our Kubernetes support policy and other supported
Kubernetes versions.

Documentation Issue

--------------------------------------------------------------------------------

AUTOMATIC RESPONSE TO LEAKED SECRETS ON ANY PUBLIC BRANCH

AUTOMATIC RESPONSE TO LEAKED SECRETS ON ANY PUBLIC BRANCH

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

If you leak a secret in a public project, it’s important to remediate it as soon
as possible. Otherwise, an adversary can abuse your account.

GitLab Secret Detection automatically responds to some types of credential leaks
in public projects by revoking the credential or notifying the partner who
issued it.

Previously, this automatic protection only worked after you committed the secret
on the default branch. Now, merge requests and other unmerged branches in public
projects are also protected by the same automatic response.

Documentation Issue

--------------------------------------------------------------------------------

DEPENDENCY SCANNING SUPPORT FOR PNPM

DEPENDENCY SCANNING SUPPORT FOR PNPM

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Thanks to a community contribution from Weyert de Boer, GitLab Dependency
Scanning now supports analyzing JavaScript dependencies managed by the pnpm
package manager.

Documentation Issue

--------------------------------------------------------------------------------

SUPPORT FOR YARN V2 AND V3 IN DEPENDENCY SCANNING

SUPPORT FOR YARN V2 AND V3 IN DEPENDENCY SCANNING

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

GitLab Dependency Scanning now supports analyzing dependencies defined in Yarn
v2 and v3 lock files. This is currently limited to the dependencies downloaded
from npm registries. Other protocols available in Yarn are not supported.

Documentation Issue

--------------------------------------------------------------------------------

GITLAB CHART IMPROVEMENTS

GITLAB CHART IMPROVEMENTS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate
 * GitLab 15.11 introduces support for Kubernetes 1.25.

Documentation

--------------------------------------------------------------------------------

SET CUSTOM GIT SERVER HOOKS USING CLI

SET CUSTOM GIT SERVER HOOKS USING CLI

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

In previous versions of GitLab, administrators needed to directly access the
file system that stored a repository to add custom Git server hooks.

Now, administrators can set Git server hooks for a repository using the new the
hooks set command in the Gitaly CLI. The Gitaly CLI command targets an
individual Gitaly node and applies the provided custom Git server hooks to the
specified repository. You can use this to programmatically roll out Git server
hooks across repositories in Gitaly.

All existing Git server hooks continue to function. However, hooks set is the
only way to configure new Git server hooks in GitLab 15.11 and later.

hooks set does not yet work for Gitaly Cluster, but this effort paves the way
for us to automatically replicate Git server hooks in Gitaly Cluster. Please
follow that effort in issue 5018.

Documentation Issue

--------------------------------------------------------------------------------

README FILES FOR GROUPS

README FILES FOR GROUPS

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Previously, README files were available only at the project level. Now, they’re
available at the group level too. As a group owner or member, you can use a
README to provide more information about your team and invite users to
contribute to your projects. In your group overview, selecting the Add README
action creates a new project (gitlab-profile) that contains the README.md file.
The README is displayed on the group overview page, and can be changed in the
group settings.

Documentation Issue

--------------------------------------------------------------------------------

BUG FIXES, PERFORMANCE IMPROVEMENTS, AND USABILITY IMPROVEMENTS

BUG FIXES, PERFORMANCE IMPROVEMENTS, AND USABILITY IMPROVEMENTS



At GitLab, we’re dedicated to providing the best possible experience for our
users. With every release, we work tirelessly to fix bugs, improve performance,
and enhance usability. Whether you’re one of the over 1 million users on
GitLab.com or using our platform elsewhere, we’re committed to making sure your
time with us is smooth and seamless.





Click the links below to see all the bug fixes, performance enhancements, and
usability improvements we’ve delivered in 15.11.



 * Bug fixes
 * Performance improvements
 * Usability improvements

--------------------------------------------------------------------------------


DEPRECATIONS DEPRECATIONS



New deprecations and the complete list of all features that are currently
deprecated can be viewed in the GitLab documentation. To be notified of upcoming
breaking changes, subscribe to our Breaking Changes RSS feed.



openSUSE Leap 15.3 packages


REMOVALS AND BREAKING CHANGES REMOVALS AND BREAKING CHANGES



The complete list of all removed features can be viewed in the GitLab
documentation. To be notified of upcoming breaking changes, subscribe to our
Breaking Changes RSS feed.



Exporting and importing projects in JSON format not supported openSUSE Leap 15.3
packages


OTHER NOTABLE CHANGES OTHER NOTABLE CHANGES

DEBIAN PACKAGE NAMING ENFORCEMENT UPDATE

DEBIAN PACKAGE NAMING ENFORCEMENT UPDATE

Starting in GitLab 15.11, Debian packages must now have a unique name and
version pair at the project level. Previously, name and version uniqueness was
enforced at the project distribution level. See issue 389228 for more details.
Existing packages with identical name and version pairs are removed on upgrade,
keeping the latest package.

--------------------------------------------------------------------------------


IMPORTANT NOTES ON UPGRADING TO GITLAB IMPORTANT NOTES ON UPGRADING TO GITLAB
15.11

To be consistent with all other data types, wiki replication and verification
now leverages the Geo self-service framework. This is a behind-the-scenes change
that will make support and maintenance easier in the future. No action is needed
from your part.

--------------------------------------------------------------------------------

Migrations to GitLab 15.11 directly from GitLab versions 15.5.0 and earlier on
self-managed installs will fail due to a missing migration until the fix for
issue 408304 is released in 15.11.1. Affected users wanting to upgrade to
15.11.x can either:

 * Perform an intermediate upgrade to any version between 15.5 and 15.10 before
   upgrading to 15.11, or
 * Target the forthcoming 15.11.1 patch.

--------------------------------------------------------------------------------


CHANGELOG CHANGELOG

Please check out the changelog to see all the named changes:

 * GitLab
 * GitLab Runner
 * GitLab Workflow for VS Code
 * GitLab CLI




INSTALLING INSTALLING

If you are setting up a new GitLab installation please see the download GitLab
page.


UPDATING UPDATING

Check out our update page.


QUESTIONS? QUESTIONS?

We'd love to hear your thoughts! Visit the GitLab Forum GitLab Forum and let us
know if you have questions about the release.


GITLAB SUBSCRIPTION PLANS GITLAB SUBSCRIPTION PLANS

 * Free
   
   Free-forever features for individual users

 * Premium
   
   Enhance team productivity and coordination

 * Ultimate
   
   Organization wide security, compliance, and planning

Try all GitLab features - free for 30 days

Cover image licensed under CC0

Share on Facebook Share on Twitter Share on LinkedIn Share on Hacker News
 * Previous Post: GitLab Patch Release: 15.10.4, 15.9.5

Sign up for GitLab's monthly newsletter
*
Enter your email address




By subscribing to this newsletter, I consent to GitLab sending me monthly blog
emails in accordance with GitLab's Privacy Statement. I may opt-out at anytime
by clicking "unsubscribe" in the email footer or by visiting our Communications
Preference Center.
























Subscribe
Having trouble viewing or submitting this form? You may need to update your
Cookie Preferences to allow all cookies. You might also need to allow us on your
adblocker, firewall, or browser privacy settings.

Thanks for subscribing!




TRY ALL GITLAB FEATURES - FREE FOR 30 DAYS

GitLab is more than just source code management or CI/CD. It is a full software
development lifecycle & DevOps tool in a single application.

Try GitLab Free
Open in Web IDE View source


PLATFORM

 * DevSecOps platform


PRICING

 * View plans
 * Why Premium?
 * Why Ultimate?


SOLUTIONS

 * Digital transformation
 * Security and governance
 * Automated software delivery
 * Agile development
 * Cloud transformation
 * SCM
 * CI/CD
 * DevSecOps
 * Value stream management
 * GitOps
 * Enterprise
 * Small business
 * Public sector
 * Education
 * Financial services


RESOURCES

 * Install
 * Quick setup checklists
 * Learn
 * Docs
 * Blog
 * Customer success stories
 * Remote
 * TeamOps
 * Community
 * Forum
 * Events
 * Partners


COMPANY

 * About
 * Jobs
 * Leadership
 * Team
 * Handbook
 * Investor relations
 * Trust Center
 * Newsletter
 * Press


CONTACT US

 * Contact an expert
 * Get help
 * Customer portal
 * Status
 * Terms of use
 * Privacy statement
 * Cookie Preferences

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is
under license

View page source — Edit in Web IDE — please contribute.

© 2023 GitLab B.V.

 * 
 * 
 * 
 * 




THIS WEBSITE USES COOKIES

We use cookies to make our websites and services operate correctly, to
understand how visitors engage with us and to improve our product and marketing
efforts. See our cookie policy for more information.Cookie Policy

Cookies Settings Accept All Cookies



PRIVACY PREFERENCE CENTER




 * YOUR PRIVACY


 * STRICTLY NECESSARY COOKIES


 * FUNCTIONALITY COOKIES


 * PERFORMANCE AND ANALYTICS COOKIES


 * TARGETING AND ADVERTISING COOKIES

YOUR PRIVACY

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
Cookie Policy

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, enabling you to securely log into the site, filling in forms, or
using the customer checkout. GitLab processes any personal data collected
through these cookies on the basis of our legitimate interest.

Cookies Details‎

FUNCTIONALITY COOKIES

Functionality Cookies


These cookies enable helpful but non-essential website functions that improve
your website experience. By recognizing you when you return to our website, they
may, for example, allow us to personalize our content for you or remember your
preferences. If you do not allow these cookies then some or all of these
services may not function properly. GitLab processes any personal data collected
through these cookies on the basis of your consent

Cookies Details‎

PERFORMANCE AND ANALYTICS COOKIES

Performance and Analytics Cookies


These cookies allow us and our third-party service providers to recognize and
count the number of visitors on our websites and to see how visitors move around
our websites when they are using it. This helps us improve our products and
ensures that users can easily find what they need on our websites. These cookies
usually generate aggregate statistics that are not associated with an
individual. To the extent any personal data is collected through these cookies,
GitLab processes that data on the basis of your consent.

Cookies Details‎

TARGETING AND ADVERTISING COOKIES

Targeting and Advertising Cookies


These cookies enable different advertising related functions. They may allow us
to record information about your visit to our websites, such as pages visited,
links followed, and videos viewed so we can make our websites and the
advertising displayed on it more relevant to your interests. They may be set
through our website by our advertising partners. They may be used by those
companies to build a profile of your interests and show you relevant
advertisements on other websites. GitLab processes any personal data collected
through these cookies on the basis of your consent.

Cookies Details‎
Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

 * View Third Party Cookies
    * Name
      cookie name


Clear
checkbox label label
Apply Cancel
Confirm My Choices
Allow All


Close


suggested results