Skip to content

Accept All すべて承認

GitLab Blog

20 stories

GitLab BlogGitHubRedesign how your team ships software with AI agents AI agents are sending more and more code into review queues built for human-paced work. A coding assistant can speed up code writing, but it can’t show you whether review, security checks, and…

GitLab BlogGitHubUncover the business logic vulnerabilities SAST scanners miss Broken object-level authorization ranks first on the OWASP API Security Top 10 , and OWASP says that traditional static application security testing (SAST) tools struggle to find access control…

GitLab BlogGitHubAI Governance: One view of agent activity AI coding agents are writing and changing code, from GitLab Duo Agent Platform agents to externally connected agents like Claude Code, Cursor, and Codex.

GitLab BlogGitHubThree developer tasks worth handing to an agent You already have an AI assistant. It completes your code, explains code you didn’t write, and maybe even drafts a whole feature while you sip your coffee.

GitLab BlogGitHubBuilding AI security in the open When code becomes abundant trust becomes scarce. That is the argument GitLab CEO Bill Staples made in his recent essay : AI is collapsing the cost of producing software, and everything around…

GitLab BlogGitHubGitLab Secrets Manager: Govern secrets like your code Credentials often start in an engineer's local dev environments, then get copied into unscoped CI/CD variables to keep pipelines running.

GitLab BlogGitHubGet every merge request in front of the right reviewer, faster The code is written. Now who reviews it? The volume of code has never been greater, but delivery hasn’t kept pace.

GitLab BlogGitHubConnect your agents to your software lifecycle with the GitLab MCP server Agents are working across your team's software development lifecycle, but most still operate as separate tools, leaving the context, handoffs, and permissions for your team to stitch together.

GitLab BlogGitHubUnblock agentic software delivery with governed code review AI agents have changed how much code a team can produce in a day. Review queues haven’t kept up, and delivery stalls while changes wait for a closer look.

GitLab BlogGitHubGitLab 19.5 released We are excited to recognize Dhairya , a Level 3 contributor, as this month’s Notable Contributor !

GitLab BlogGitHubGemini 4 Argon on GitLab: Built for long-running agentic work As AI models take on longer, multi-step work, the challenge is putting that power to use across the software lifecycle without adding risk or cost.

GitLab BlogGitHubScaling Git for the agentic software factory AI agents are fundamentally changing the economics of software development. As the cost of producing code falls, the volume of changes moving through the software factory is accelerating beyond what…

GitLab BlogGitHubMake every AI credit count: See, cap, and reduce agent spend Costs multiply with every task you hand to an agent. Each task consumes tokens and credits, and as agents spread across your teams and automations, consumption can grow faster than usage.

GitLab BlogGitHubGitLab's agent orchestration eliminates the wait between development stages AI coding tools have changed how fast software gets written, but not how fast it ships. As code generation accelerates, the bottleneck moves downstream into verify, review, and ship.

GitLab BlogGitHubGitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8 On October 12, 2026, we released versions 19.4.2, 19.3.5, 19.2.8 for GitLab Community Edition (CE) and Enterprise Edition (EE).

GitLab BlogGitHubTrack organization-wide security risk in one dashboard If you run application security across more than one top-level group, getting a single organization-wide view of your risk has meant manually pulling together data.

GitLab BlogGitHubGitLab Transcend: Speed you can trust, all the way to production At Transcend, we made over a dozen announcements across all four layers of our architecture for agentic software engineering: agent orchestration, data and context, DevOps workflows, and governance…

GitLab BlogGitHubDependency Firewall: Block risky packages before the build Attackers disguise malicious packages as ones you trust. In June 2026, GitLab researchers found five malicious PyPI packages , four of them typosquats of Flask, Requests, and NumPy, that run at…

GitLab BlogGitHubEvery artifact your teams ship, assembled right the first time Every software build is assembled from open source packages, base images, and libraries, with your code on top. When one of those components is missing or has drifted, the build fails.

GitLab BlogGitHubTwo front doors: Module-level access in a Django GRC app GitLab's engineering team builds a lot of our own internal tooling, but one platform in particular forced us to rethink how we handle authorization: our internal GRC tool that serves two very…

On the calendar

予定 · Conferences and launch events, this week's stories from each corner of the industry, and what its press is covering — in English

On view

This week, from that corner the newest stories from the corner of the industry you picked

The wire their own posts, translated

How code moves in 2026 from the industry's own reports

Sources

Fetched every six hours, linked to the original

About

The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo