GitLab 19.1 release notes | GitLab Docs

GitLab 19.1 release notes

On June 18, 2026, GitLab 19.1 was released with the following features.<br>We&rsquo;d also like to announce this month&rsquo;s Notable Contributor: Pishel65!<br>We are excited to recognize Pishel65, a Level 3 contributor with 19 merged MRs and 9 more open since joining in October 2025.<br>Primary features<br>Secret false positive detection with GitLab Duo<br>Tier: Ultimate<br>Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government<br>Links: Documentation · Related Issue

Secret false positive detection with the GitLab Duo Agent Platform is now generally available.<br>Security teams spend significant time investigating secret detection findings that are incorrectly flagged as actual secrets.<br>These false positives create alert fatigue, erode trust in scan results, and divert attention from genuine security risks.<br>When a security scan runs, GitLab Duo automatically analyzes each critical and high severity secret detection vulnerability to determine if it is a false positive.<br>The AI assessment appears in the vulnerability report, so you have immediate context for faster and more confident triage decisions.<br>Key features include:<br>Automatic analysis: Runs after each security scan without manual trigger.<br>Manual trigger: Trigger false positive detection for individual vulnerabilities on the vulnerability details page for on-demand analysis.<br>Focus on high-impact findings: Analyze only critical and high severity vulnerabilities to maximize signal-to-noise improvement.<br>Contextual AI reasoning: Each assessment includes an explanation of why the finding is likely a true positive, based on code context and vulnerability characteristics.<br>Confidence scoring: Each detection includes a confidence score to help teams prioritize review based on the model&rsquo;s certainty.<br>Seamless workflow integration: Results appear directly in the vulnerability report alongside existing severity, status, and remediation information.<br>We welcome your feedback in issue 592861.

Always on availability mode for GitLab Duo<br>Tier: Premium, Ultimate<br>Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government<br>Links: Documentation · Related Issue

Administrators can now set GitLab Duo to be always on for all projects in an entire instance or top-level group. When GitLab Duo is set to always on,<br>group, subgroup, and project owners cannot turn off GitLab Duo, giving enterprises centralized AI governance for compliance and<br>regulated environments.<br>This new setting is symmetrical to the existing always off setting, closing a gap where GitLab Duo could<br>be locked off but could not be locked on. This new setting is especially valuable for organizations with autonomous divisions or subsidiaries that<br>need to guarantee consistent AI tooling across the business.<br>To set GitLab Duo to be always on, go the instance or top-level group GitLab Duo settings and set GitLab Duo availability to Always on .

Automatically assign Code Owners as reviewers<br>Tier: Premium, Ultimate<br>Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated<br>Links: Documentation · Related Issue

Previously, you needed to select reviewers for each merge request manually,<br>even when a CODEOWNERS file already defined who should review each file.<br>You can now configure a project to assign Code Owners as reviewers automatically.<br>GitLab assigns every Code Owner that matches the changed files. This happens when a<br>merge request is created in a ready state, or when a draft is marked ready. If you<br>already assigned a reviewer, GitLab skips automatic assignment and keeps your choice.<br>To turn on automatic reviewer assignment, go to Settings > Merge requests ><br>Automatic reviewer assignment and select Automatically assign all code owners as<br>reviewers .

Compliance framework templates (beta)<br>Tier: Ultimate<br>Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government<br>Links: Documentation · Related Issue

You can now create compliance frameworks from predefined templates.<br>Previously, building a compliance framework required defining every requirement and control by hand, a<br>repetitive process when a framework had dozens of controls.<br>Now, when you create a new framework in the Compliance center, you can:<br>Select Create from template to start from a preconfigured framework with requirements and controls<br>already in place.<br>Preview each template, customize the name, description, and color, and then apply it to your group in a<br>single step.<br>19 templates are available, including ISO 27001:2022, SOC 2, FedRAMP, NIST, CIS, TISAX, and more.

Improved secret detection coverage for feature branch pipelines<br>Tier: Free, Premium, Ultimate<br>Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government<br>Links: Documentation · Related Issue

In GitLab versions earlier than 19.1, you couldn&rsquo;t trust a feature branch pipeline to<br>surface every secret in your...