Ever had a build fail because a public repository went down? Been there. Never doing that again with Artifact Central caching our packages 🥳
Watch the full demo here to see how pulling the same packages took less than half the time 👉 about.gitlab.com/blog/transc…
A little less pressure to keep up. A little more focus on moving forward together 🚀
@Steve_Yegge shares why AI adoption needs a human pace and how AI can help teams find a shared language.
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 release approvals can keep pace with all that extra code.
AI-native engineering is the practice of intentionally designing the engineering process so people and agents each do what they are best suited to. It starts with identifying delivery bottlenecks, then deciding how much autonomy agents should have and how to maintain control as you scale.
Read the blog to learn more: about.gitlab.com/blog/redesi…
ALT Promotional image for GitLab's "AI-Native Engineering Playbook." It includes headlines about AI changing how code is written and suggests exploring the Playbook to change team workflows. The GitLab logo is visible at the bottom.
Get every merge request in front of the right reviewer, faster.
Most organizations do not lack capable reviewers. They lack a consistent way to get each merge request in front of the right one. With Recommend Reviewers Flow, now generally available in GitLab 19.5, GitLab recommends the best individual reviewer when you create a merge request, based on workload, time zone, availability, and expertise defined by approval rules and CODEOWNERS. The flow explains why it chose each reviewer and lets you assign them in one click, so reviews start sooner and review load spreads across every qualified engineer.
Read the blog: about.gitlab.com/blog/recomm…
GitLab Secrets Manager is now generally available.
Built on OpenBao, it keeps build-time and runtime secrets under the permissions and audit trail that govern your code. Each secret reaches only the jobs that declare it and fall within its scope.
Learn more. about.gitlab.com/blog/secret…
The GitLab MCP server is now generally available.
Any MCP-compatible agent can run core GitLab workflows from the client your team already works in, with dozens of tools across code, merge requests, work items, and pipelines. Each action runs under your existing GitLab permissions.
Read the blog to learn more. about.gitlab.com/blog/mcp-se…
Speed you can trust, all the way to production.
With GitLab 19.5, you connect any MCP-compatible agent to GitLab from the client your team already uses. You keep secrets under your existing permissions and get every merge request to the right reviewer, faster.
Learn more about the 19.5 release: about.gitlab.com/whats-new