IT Brief India - Technology news for CIOs & IT decision-makers
India
GitLab 19.6 adds security fixes, Slack tools & automations

GitLab 19.6 adds security fixes, Slack tools & automations

Fri, 20th Nov 2026 (Today)
Joseph Gabriel Lagonsin
JOSEPH GABRIEL LAGONSIN News Editor

GitLab has released version 19.6 of its DevSecOps platform, adding tools for security remediation, workflow automation, Slack integration and credit usage.

The update is aimed at helping software, security and product teams hand more routine and remedial work to software agents while keeping closer oversight of what those agents do and what they cost.

One of the main additions is broader use of agentic remediation for security findings. Security managers can now enable agent flows across multiple projects at once, while development teams can run those flows on branches other than the default branch to address findings before code is merged.

A new vulnerability context flow, released in beta for SAST findings, is designed to show whether a flaw is exploitable in practice. That should let teams rank issues by exploitability as well as severity, helping organisations decide which findings to fix first.

GitLab has also added a mean time to remediation chart and group-level policies that can hold changes containing critical or known-exploited vulnerabilities until a designated approver signs them off.

Another security feature focuses on exposed credentials. When secret detection identifies an active GitLab personal access token, teams can now rotate the token and remediate the code in one step. The rotate-and-fix function, now in beta on GitLab.com, revokes the leaked token, creates a replacement with the same permissions, stores it in GitLab Secrets Manager and opens a merge request to remove the hardcoded token from source code.

Manav Khurana, Chief Product and Marketing Officer at GitLab, framed the changes around rising pressure on security teams.

"Every organisation is racing to keep up with the security challenges that have become the new norm," said Manav Khurana, Chief Product and Marketing Officer at GitLab. "GitLab 19.6 helps security teams clear vulnerability backlogs faster, and provides new automations. Both of which are easier to afford now that each GitLab Credit can be used for more agentic work."

Scheduled tasks

GitLab is also introducing scheduled automations in beta. The feature allows GitLab Duo Agent Platform flows to run in the background on a recurring basis, at intervals ranging from every 15 minutes to every three months.

It can be used for tasks such as daily issue triage or hourly checks on CI health. Each automation runs through a dedicated service account with scoped permissions, and audit events record the activity separately from human actions.

A redesigned Automations page is intended to show what has run, how often it has succeeded and why a run failed. That visibility is meant to make recurring agent-driven work easier to monitor and govern.

Slack link

Another part of the release is GitLab for Slack, now generally available on GitLab.com for Premium and Ultimate customers. The integration lets users mention @GitLab in a Slack thread or direct message to create issues, merge requests and agent flows, with results posted back to the thread.

According to GitLab, each request runs with the user's own GitLab permissions and creates an agent session inside GitLab. Any merge requests created through Slack still go through the usual review, approval and audit processes.

Slack said the integration reflects the reality that many software decisions begin in workplace messaging tools before being entered into engineering systems.

"Teams make decisions in Slack every day, and the best agents are the ones that can act on that context," said Katie Steigman, Vice President of Product Management at Slack. "GitLab for Slack lets agents read the conversation, take action across the software lifecycle in GitLab, and bring the results back to the thread. Teams can go from a quick discussion to planned, reviewed, and shipped work without switching tools."

Credit changes

GitLab also said it has made usage on its Duo Agent Platform more efficient, so each task now requires fewer model requests. As a result, most customers will see their GitLab Credits stretch up to twice as far.

The revised credit economics are intended to support heavier use of newer agent-based features, including remediation flows, scheduled automations and Slack-based actions. Customers on Flex contracts can also direct credits towards other products, including GitLab Secrets Manager and Dedicated Hosted Runners.

Beyond the headline features, version 19.6 includes new MCP governance controls in beta, including settings to always allow, always ask or always deny specific tools, with an audit event created for every tool call. The release also adds flow suggestions when external MCP clients connect, a generally available Rapid Diffs view that GitLab said loads the first file about three times faster, and support for resumable jobs and auto-merge time windows.

Overall, the changes extend GitLab's push to make agent-based software work more routine within development and security workflows while maintaining approval checks and activity records.