正式なドキュメントは英語版であり、この日本語訳はAI支援翻訳により作成された参考用のものです。日本語訳の一部の内容は人間によるレビューがまだ行われていないため、翻訳のタイミングにより英語版との間に差異が生じることがあります。最新かつ正確な情報については、英語版をご参照ください。
ドキュメントに関する現在のご利用体験についてお聞かせください。アンケートにご協力ください。

GitLab 19.6(リリース予定)

以下の機能がGitLab 19.6で提供されます。 これらの機能はGitLab.comでご利用いただけます。

注目のコントリビューター

今月の注目のコントリビューターとして、レベル5のコントリビューターであるJoséさんをご紹介します!

Joséさんは、GitLab GraphQL API全体にわたって、きめ細かいパーソナルアクセストークンの認可を体系的に拡張しました。これにより、きめ細かいトークンを使用して、blame、CODEOWNERSの検証、利用可能なデプロイキー、プロジェクトのセキュリティ指標などのデータを読み取れるようになりました。

主要機能

AIエージェント向けGitLab MCPサーバーツールのガバナンス

AIエージェントが使用できるGitLab MCPサーバーツールを制御できるようになりました。設定したルールは、接続するすべてのクライアントにGitLabが適用します。

トップレベルグループのオーナーは、各ツールに次のいずれかを設定できます。

  • 常に拒否: ツールは完全にブロックされ、エージェントからは見えません。
  • 常に確認: ツールを実行する前に、ユーザーの承認が必要です。
  • 常に許可: ツールは通常どおり実行されます。

この機能はベータ版です。フィードバックはイシュー633490をご覧ください。

Audit events for MCP server tool calls

Every action an agent takes through the GitLab MCP server now creates an audit event. You get a record of agent activity without adding any client-side tracking.

Each event records who performed the action, what they did, which resource was affected, and when. Events are also marked as coming from the MCP server, so you can tell agent actions apart from actions people take directly.

To review these events, go to AI > Governance in your top-level group and select the Audit events tab. Security and compliance teams get a complete view of what external agents do in GitLab.

Review merge requests faster with Rapid Diffs

In previous versions of GitLab, even small merge requests made you wait for the first diff to load. Large ones could slow down or freeze the page.

Rapid Diffs, a ground-up rewrite of how GitLab renders diffs, is now generally available and replaces the classic diff view. GitLab renders diffs on the server and streams them to your browser, so reviews start in seconds:

  • The first file appears in about 1.5 seconds, down from about 4.5 seconds.
  • Browser search (Control+F or Command+F) works right away, without freezing the page.

Rapid Diffs also supports the review tools you already use:

  • File-by-file mode
  • Mark as viewed
  • Full file view
  • Commit-by-commit navigation
  • Keyboard shortcuts
  • Image comments

エージェント型コア

`/goal` command in GitLab Duo Agentic Chat

Previously, GitLab Duo Agentic Chat in the GitLab UI answered one message at a time and waited for you to continue. For a larger change, like fixing a set of failing tests, you had to keep prompting it.

Now you can start a long-running task with /goal. Agentic Chat starts a Developer Flow session that keeps working until the task is done, so you don’t have to prompt after each step.

The flow can commit, push, and create merge requests without asking you to approve each action. Each goal also uses compute minutes.

To use /goal, open Agentic Chat in a project and turn on the Developer Flow for your top-level group.

Fail flows when the sandbox is unavailable

In previous versions of GitLab, a GitLab Duo Agent Platform flow in a runner environment ran without isolation if the sandbox was unavailable, and you saw only a warning. Now you can make the job fail instead of running the flow without the sandbox.

Provide images as context with self-hosted models

In previous versions of GitLab, the Developer Flow and Agentic Chat did not support images as context with self-hosted models.

Now, they can read screenshots and diagrams from your repository and attachments with any self-hosted model that supports image input.

If your model cannot read images, an administrator can declare it in the AI Gateway model metadata file. The AI Gateway then replaces each image with a text notice before it sends the request.

Start flow sessions faster with a reference repository (Beta)

In previous versions of GitLab, every flow session cloned your whole repository first, so large projects waited minutes before the agent started. Now you can include a copy of your repository in the image used for GitLab Duo Agent Platform sessions, so each session fetches only recent commits and starts significantly faster.

Web search in GitLab Duo Agentic Chat

Previously, GitLab Duo Agentic Chat couldn’t look up current information. It answered only from the model’s training data and your GitLab context. Answers about things like the latest package version or a security advisory might be out of date.

Now you can turn on web search in a conversation. Chat searches the web and reads pages to find current answers, so you don’t have to leave GitLab. Expand each search in the conversation to see the pages it found. Each search also creates an audit event.

Web search is off by default. On GitLab.com, a group Owner must allow it for the top-level group. On GitLab Self-Managed and GitLab Dedicated, an administrator must allow it for the instance.

Workspace subagents are generally available

Workspace subagents, previously released as an experiment, are now generally available.

Use workspace subagents to keep the details of a task, like linter output, out of the context of the Developer Flow. Or use them for a separate agent with its own instructions and limited tools.

Define subagents as Markdown files in the .agents/agents/ directory at the root of your repository. The Developer Flow decides when to delegate a task to one, and receives only the result.

In GitLab Duo CLI 10.2.0 or later, use /agents to list subagents and ask the Developer Flow to use one. In an issue or merge request comment, mention the Developer Flow and ask it to list subagents or delegate a task to one.

Automate routine work with scheduled automations (beta)

In previous versions of GitLab, a flow started only when a person or an event kicked it off. Without one, routine work like issue triage waited.

Now scheduled automations give that work a dependable rhythm. Set the cadence once, from every 15 minutes to monthly, and a flow runs on its own at the times you choose. Triage new issues every morning, or check pipeline health every hour.

Each scheduled automation runs as a dedicated service account with a scoped role, so its actions are attributed to that account, not a person.

Triggers are now called automations. The redesigned Automations page brings scheduled and event-based automations together, with run history, success rates, and session details.

To try it, turn on experiment and beta features.

GitLab Duo approves or requests changes (beta)

In previous versions of GitLab, Code Review Flow could only leave comments. It could not approve or block a merge.

Now GitLab Duo can approve or request changes based on its review:

  • With nothing to comment on, GitLab Duo approves the merge request. The approval does not count toward required approvals.
  • With findings to comment on, GitLab Duo requests changes. If your project blocks merges on a request for changes, a request from GitLab Duo blocks a merge too. The request stays until GitLab Duo approves in a follow-up review, or a user bypasses it.

To use this feature, turn on experiment and beta features, then turn on GitLab Duo can approve and request changes for your project, group, or instance.

統合DevOpsとセキュリティ

Automated triage and remediation profile (UI)

You can now turn on security flows across a group the same way you turn on scanners. Apply an automated triage and remediation profile from the security inventory or the new Automated Triage and Remediation tab in Security configuration. The profile turns on the SAST, secret detection, and dependency scanning flows for the projects you select.

Previously, the profile was available only through the GraphQL API. Now you pick a preset and apply it in one action. For most flows:

  • Conservative: on demand, high severity and above.
  • Standard (recommended): automatic, medium severity and above.
  • Proactive: automatic, every severity. Review credit use first.

The security inventory’s new Capabilities column shows where flows run, next to where scans run.

Configurable limits for pipeline variables

Administrators can now limit the number and size of pipeline variables that can exist in a single pipeline. This helps maintain the stability of your CI/CD infrastructure by blocking users from adding too many large pipeline variables to their pipelines.

The limits are disabled by default for GitLab Self-Managed and GitLab Dedicated. For GitLab.com, the limits are:

  • 1,200 variables per pipeline
  • 128 KiB per value
  • 1 MiB per file type value

Control how Quick setup applies scan profiles

You can now choose how the Scanner Enablement Wizard applies a scan profile to a group. Previously, Quick setup attached the profile to every project, so projects already scanning through CI/CD configuration or a policy ran the scan twice.

Quick setup now asks how to apply it:

  • All projects: Applies the profile to every project and replaces any existing profile for that scanner. Projects that scan another way run both scans.
  • Projects that don’t scan yet (recommended): Applies the profile to projects with no scan for that scanner. Projects that already scan keep their current setup.
  • Replace existing: For projects that already have a profile for that scanner, replaces it with the new one.

Customize dependency scanning profiles in the UI

You can now create and customize dependency scanning profiles in the UI, the same way as secret detection and SAST profiles. Set how dependency scanning runs once for a group, then apply it to every project without editing .gitlab-ci.yml in each one.

Previously, you could customize a dependency scanning profile only with the GraphQL API. Now go to Secure > Security configuration, select the Scanners tab, and select Manage profiles on the dependency scanning row. Choose whether scans run on merge request pipelines, default branch pipelines, or both, then add settings to override, such as paths to exclude.

Apply the profile from the security inventory or in the advanced setup of the Scanner Enablement Wizard.

GitLab MCPサーバーのOrbitツール

以前のバージョンのGitLabでは、GitLab OrbitにクエリするためにAIエージェントが別のMCPサーバー接続を必要としていました。 今回のリリースで、GitLab MCPサーバーにOrbitツールセットを追加できるようになり、エージェントはすでに使用している接続からOrbitのコンテキストを取得できます。

Advanced SAST with Rust language support

Previously, GitLab SAST had no coverage for Rust, so vulnerabilities in Rust code went undetected by your pipeline.

GitLab Advanced SAST now scans Rust code. When you turn on GitLab Advanced SAST, Rust code in your repository is analyzed automatically, with no additional configuration. Incremental scanning is on by default, so only changed code is re-analyzed between pipelines.

Advanced SAST traces untrusted input across functions and files. Findings such as SQL injection, command injection, and path traversal include a code flow from source to sink. For the weakness types covered, see additional languages CWE coverage.

Rust analysis was added in GitLab 19.5 and is in beta.

Automatic false positive detection on tracked branches

In previous versions of GitLab, false positive detection ran automatically only on vulnerabilities in the default branch. Findings on release branches and tags had to be triaged by hand.

Now, the SAST False Positive Detection Flow runs automatically on new Critical and High vulnerabilities in any tracked branch, and in tracked tags that run SAST jobs, so you can filter out noise before you merge or ship. It runs when you turn on false positive detection in your project settings, or when you use the automated triage and remediation profile set to run automatically.

Secret false positive detection on tracked branches and tags is available on GitLab.com in this release.

Business Logic Security Analyzer on GitLab Self-Managed and GitLab Dedicated

Business Logic Security Analyzer is a GitLab Duo Agent Platform flow that reasons about what your code is meant to enforce. It finds vulnerabilities that pattern-based scanners miss:

  • Broken object-level authorization.
  • Missing authorization checks.
  • Mass assignment.

Findings appear in the vulnerability report and the merge request security widget.

Until now, the Business Logic Security Analyzer was available only on GitLab.com. Organizations on GitLab Self-Managed and GitLab Dedicated, which often have the strictest requirements for where code is analyzed, couldn’t use it.

Now it runs on both:

  • On GitLab Dedicated, scans run on GitLab-hosted runners.
  • On GitLab Self-Managed, scans run on your runners.

To get started, contact your account team.

Each scan consumes GitLab Credits. For setup, see Business logic scanning.

Dependency scanning auto-remediation with Swift support and runner tags

Dependency scanning auto-remediation opens merge requests that bump the versions of vulnerable dependencies. Previously, Swift projects were not supported, and the job ran only on untagged runners. Merge requests went to a random maintainer, and each project could have at most 10 open at once.

In GitLab 19.6:

  • Swift Package Manager projects with a committed Package.resolved file now get auto-remediation merge requests.
  • You can set runner tags on an auto-remediation profile and the job runs on matching runners.
  • With automatic reviewer assignment turned on, the Code Owners of the updated files are requested as reviewers. Otherwise, GitLab assigns no reviewer.
  • Each project can have up to 30 open auto-remediation merge requests.
  • Titles and commit messages follow Conventional Commits when your repository does.

For details, see dependency scanning auto-remediation.

Filter group vulnerability reports by security attributes

In earlier versions of GitLab, you could not filter the group vulnerability report by application, business unit, or team. Now, you can filter by the security attributes assigned to your projects.

Each security category, such as Business impact or Application, appears as its own filter. Select is one of to include attributes or is not one of to exclude them. Use these filters to review every vulnerability for one application, even when it spans many projects.

This filter requires advanced vulnerability management.

Set vulnerability due dates on the details page

In previous versions of GitLab, you could set and view vulnerability due dates only through the GraphQL API.

Now, you can view and set a vulnerability’s due date from the vulnerability details page. While the vulnerability has the Needs triage or Confirmed status, GitLab labels the date:

  • overdue, after the date passes.
  • due soon, when the date is in the next seven days.

Track mean time to remediate in security dashboards

In previous versions of GitLab, you couldn’t see how quickly your teams fix vulnerabilities over time.

Project, group, and organization security dashboards now include a mean time to remediate (MTTR) chart. It shows the weekly MTTR over the last 12 weeks, with the number of vulnerabilities remediated each week. To find where remediation slows down, group the chart by severity or report type. Compare the trend against your remediation SLAs.

MTTR counts recently detected vulnerabilities that were resolved or are no longer detected. Dismissed vulnerabilities are excluded.

悪意のあるパッケージを追加するマージリクエストをブロックする

以前のバージョンのGitLabでは、マージリクエスト承認ポリシーは悪意のあるパッケージを他の脆弱性と同様に扱っていました。検出結果が無視された場合や、ルールの重大度フィルターの範囲外となった場合、害を引き起こすために作られたパッケージであってもマージされる可能性がありました。

今回のリリースで、マージリクエスト承認ポリシーにマルウェアルールを追加できるようになりました。依存関係スキャンがGitLabのマルウェアアドバイザリに記載されているパッケージを検出した場合、検出結果の重大度や状態に関わらず、マージリクエストには承認が必要となります。マルウェアルールは既存のスキャン検出ルールと併用できるため、既存のポリシーを作り直すことなく追加できます。

マルウェアルールを使用するには、プロジェクトで SBOMを使用した依存関係スキャン を実行する必要があります。マルウェアアドバイザリは、npm、PyPI、Maven、Go、NuGet、Cargo、およびRubyGemsパッケージに対応しています。

スケールとデプロイ

NGINX updated to 1.31.7 in the Linux package

GitLab 19.6 updates the NGINX version bundled in the Linux package from 1.31.4 to 1.31.7. This update fixes five security issues: CVE-2026-15176, CVE-2026-93479, CVE-2026-95101, CVE-2026-97629, and CVE-2026-97205.

The configuration the Linux package generates is not affected. If you added custom NGINX configuration, two upstream changes might break it:

  • Zero-size buffer settings are now rejected.
  • IP-address certificate verification now matches only IP subject alternative names.

Before you upgrade, review your custom configuration. For more information, see the upgrade notes.

Non-billable usage across the GitLab Credits dashboard

The GitLab Credits dashboard summary cards and chart include non-billable usage, such as usage covered by a promotion. Previously, the per-user and per-product breakdowns counted billable usage only, so they didn’t add up to the totals. The user list also skipped anyone with only non-billable usage.

GitLab now counts non-billable usage in:

  • The Usage by user and Usage by product tabs.
  • The user drill-down, where a badge on each non-billable event shows the reason.
  • Your personal GitLab Credits usage page on GitLab.com.

Co-created contributions

Set a time window for automatic merge

You can now set a time range for a merge schedule to merge automatically. In previous versions of GitLab, the merge schedule supported only the After option, which prevented a merge before the date you set. Now you can select Between to define a window: the merge request merges only when the current time falls between the two dates you set.

Thank you to Niklas van Schrick for these contributions (MR 1 MR 2 MR 3)!

Restrict Jira Cloud domain access

Administrators can now configure a domain allowlist for the GitLab for Jira Cloud app. Jira sites that are not on the allowlist can’t install the app. Upgrading or reinstalling the app also fails for those sites, so add every Jira site that is already connected before you save the allowlist. An empty allowlist allows all domains, preserving the previous behavior. The allowlist applies only to the Connect version of the app, not the Forge version.

Thank you to Roger Meier for this contribution (MR)!

Group ID for feature flag rollout strategies

The percent rollout and percent-of-users feature flag strategies now accept a custom Group ID. Strategies across flags that share the same Group ID and stickiness value select the same user set at the same percentage, letting you coordinate rollout across multiple flags. Change the Group ID to target an independent set of users instead.

Thank you to Mehdi Youb for this contribution (MR)!

MCPサーバーでGitLab Pagesのコンテンツを読み取る

以前のバージョンのGitLabでは、GitLab MCPサーバーでPagesサイトのソースを読み取ることができましたが、パイプラインによってビルドされたサイト自体は読み取れませんでした。get_pages_contentツールを使用することで、GitLab MCPサーバーは指定したPages URLの公開コンテンツを読み取れるようになりました。閲覧権限を持つプライベートPagesサイトも対象となります。

このコントリビュートをいただいたMawueliさんに感謝します!

Work item types in MCP project details

In previous versions of GitLab, your AI agents needed a separate request to learn which work item types a project supports. Now your agents get a project’s work item types and the fields each type supports in the same request as the project details.

Thank you to Aditya Parida for this contribution!

Workspaces support ARM64 Kubernetes clusters

GitLab Workspaces now run native images on linux/arm64 Kubernetes nodes, including Apple M-series hardware. Previously, arm64 nodes ran the amd64 image under emulation. GitLab pulls the correct image variant for each node automatically. Custom devfile images must support the architecture of the node where the workspace runs.

Thank you to Miguel Sacristan for this contribution (MR)!

Archive subgroup custom role ability

You can now add the archive_subgroup ability to custom roles. Users with this ability can archive and unarchive subgroups without needing the broader Owner role, which also grants the ability to delete a group. The ability appears as Archive subgroup in the custom role editor.

Thank you to Jimmy Spagnola for this contribution (MR)!

Status-based board lists in the REST API

The board list REST API endpoints now accept a status_id parameter, letting you create board columns that filter issues by a custom status. The API response includes the full status object so your automation can read back the status it set. In previous versions of GitLab, status-based lists could not be created through the REST API.

Thank you to Daniel Ziegenberg for this contribution (MR)!

New community tools in the MCP server

Community contributors added 10 new capabilities to the GitLab MCP server for 19.6:

CITATION.cff file detection

GitLab now detects CITATION.cff files in repositories. Projects with a CITATION.cff file show a link to the file in the project overview. Projects without one show an option to add a CITATION.cff file. CITATION.cff is an open file format that describes how to cite software.

Thank you to rajasekhar for this contribution (MR)!

Other improvements

Community contributors made many improvements, including:

  • The merge widget no longer briefly shows failed checks while a merge is in progress. (Aleksandr Kotlyar, MR)
  • Footnotes cited more than once now all link correctly. (José M. Requena Plens, MR 1 MR 2)
  • The Starred tab on user profiles is now paginated. (Radek Antoniuk, MR)
  • Jobs with needs: dependencies now appear in the correct column in the pipeline dependency view. (iDang3r, MR)
  • Group subproject and members lists now show the effective role. (Gerardo Navarro, MR 1 MR 2)
  • The Dependency Proxy now falls back to cached images during Docker Hub outages. (Tri Lam, MR)
  • Cached Dependency Proxy blobs are now served without requesting an upstream token. (Thota Shashank, MR)
  • Telegram notifications now HTML-escape project titles and branch names. (kuttLoggin, MR)