GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8
No short summary was recorded for this item; read the full text at the source.
This page shows only the headline and the short summary. The full text is published by the original source.
Related news
Full archive →
GitLab Blog
The Pentagon wants to know who checks code when AI writes it
The Department of War now treats AI-generated code as unverified until it’s proven otherwise. DoW Instruction 8430.01, “Accelerated Mission Software,” took effect September 8, 2026, and is the department’s latest guidance on modernizing and managing software. If you build or buy software for the DoW, the instruction changes what’s required of you for every line AI writes. You have to review and test it to the same st…
GitLab Blog
GitLab Orbit: Find vulnerability blast radius without the manual hunt
A critical vulnerability needs a fix and a map. The fix is usually fast. Finding where the vulnerable component lives, who owns it, and whether it's exposed to the Internet is what costs you time. Most security teams piece that answer together from scanner reports, spreadsheets, and a Slack thread asking who owns a service nobody recognizes, and you stay exposed for every hour that takes.GitLab Orbit, now generally a…
GitLab Blog
GitLab Orbit is GA: Higher agent accuracy, lower token cost
An agent’s true cost isn’t only the tokens it burns. It’s the review that calls your code “safe to merge” after seeing the diff, but without any context on the pipeline. We call that artificial confidence, not artificial intelligence. Agents guess because code is all they can see; they can’t see the merge request that last changed it, the pipeline that ran it, the vulnerability it carries, or the people who wrote and…
GitLab Blog
Extend GitLab Duo Agent Platform into your business systems
Developers mostly use GitLab Duo Agent Platform where they already work: the IDE, merge requests, and issues. But DevSecOps teams also support the business systems the rest of the company runs on, and those systems break too.In Salesforce, for example, when a validation fails, a callout times out, or a null slips through a trigger, the error gets logged, but the log doesn’t explain the cause. An engineer still has to…