GitLab Blog
Featured blog posts
Security
GitLab Secrets Manager: Govern secrets like your code
Tighten credential security by scoping build-time secrets to the jobs that need them and serving runtime secrets from the same store. Generally available in GitLab 19.5.
AI
Get every merge request in front of the right reviewer, faster
GitLab 19.5 recommends the right reviewer for every merge request, so reviews start sooner and route faster, and DevOps teams can ship more changes.
AI
Connect your agents to your software lifecycle with the GitLab MCP server
Run GitLab workflows from your favorite AI application in fewer calls and with leaner context. The GitLab MCP server is now generally available.
Recent posts

GitLab 19.5 released
This release includes GitLab MCP server and GitLab Secrets Manager as generally available, and new AI governance capabilities.
Browse by category

Agile planning gets a boost from new features in GitLab 18.10
Work items list and saved views reduce context switching, keeping your software development team aligned and their workflows efficient.
Ace your planning without the context-switching
Embedded views: The future of work tracking in GitLab

Get every merge request in front of the right reviewer, faster
GitLab 19.5 recommends the right reviewer for every merge request, so reviews start sooner and route faster, and DevOps teams can ship more changes.
Connect your agents to your software lifecycle with the GitLab MCP server
Unblock agentic software delivery with governed code review

curl removed from Omnibus-GitLab FIPS packages in 19.0
With the Omnibus-GitLab 19.0 release, GitLab will stop building curl for FIPS customers. Here’s what you need to know.
Claude Opus 4.7 is now available in GitLab Duo Agent Platform
Passkeys now available for passwordless sign-in and 2FA on GitLab

The Co-Create Program: How customers are collaborating to build GitLab
Learn how organizations like Thales, Scania, and Kitware are partnering with GitLab engineers to contribute meaningful features that benefit the entire community.
Kingfisher transforming the developer experience with GitLab
How Indeed transformed its CI platform with GitLab

How to design GitLab for enterprise scale
Plan an enterprise rollout with clear choices for deployment, runner capacity, availability, disaster recovery, and pipeline performance.
How to calculate DevOps platform total cost of ownership
Consolidate your GitLab stack with Gitaly on Kubernetes

Two front doors: Module-level access in a Django GRC app
A technical deep-dive on restructuring a Django internal tool to support two distinct GitLab teams: Security Compliance and Internal Audit.
How GitLab reduced code-per-agentic-flow ratio by 45%
Co-Create: Building GitLab with our users

When code is abundant
Producing code is getting cheap. Trusting it is not. Why enterprises need a durable layer of context, verification, and governance around AI agents.
GitLab named a Leader in the 2026 Gartner® Magic Quadrant™ for DevSecOps Platforms
GitLab and Capgemini accelerate DevSecOps transformation

What's new in Git 2.56.0?
Learn about the new features and changes in the latest Git release, including a new git-history(1) drop command, git-refs(1) getting new subcommands to modify refs, linearizing history with git-replay(1), and more.
How to recognize your team with GitLab Achievements
What's new in Git 2.55.0?

GitLab 19.5 released
This release includes GitLab MCP server and GitLab Secrets Manager as generally available, and new AI governance capabilities.
GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8
GitLab Transcend: Speed you can trust, all the way to production

GitLab Secrets Manager: Govern secrets like your code
Tighten credential security by scoping build-time secrets to the jobs that need them and serving runtime secrets from the same store. Generally available in GitLab 19.5.
Track organization-wide security risk in one dashboard
Dependency Firewall: Block risky packages before the build

DeepSeek-Reasonix: How a poisoned config can hijack an AI coding agent
GitLab's Threat Research Group found a flaw, ConfigPoisoning, that runs attacker code when a developer views a file's diff in DeepSeek-Reasonix.


