GitLab Blog
Featured blog posts
Security
GitLab Orbit: Find vulnerability blast radius without the manual hunt
Exploitation happens at machine speed now. Map every project, owner, and pipeline a critical CVE touches so remediation can keep up.
Security
What happens when vulnerabilities are discovered faster than you can fix them?
Frontier AI is changing how quickly vulnerabilities can be discovered and exploited. The next challenge is bringing that same speed to remediation and prevention, inside the software factory.
AI
Extend GitLab Duo Agent Platform into your business systems
Learn how to call a custom GitLab flow from Salesforce so every error arrives as a GitLab issue with root-cause analysis, ready to fix and deploy.
Recent posts

Pillow CVE-2026-112900: How to find and fix it with GitLab
Upgrade to Pillow 13.0.0, then use dependency scanning, code search, and GitLab Duo Agent Platform to patch every affected Python project in your groups.
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

GitLab Orbit is GA: Higher agent accuracy, lower token cost
Your entire software lifecycle in one queryable graph, with permissions intact. In GitLab testing, agents on GitLab Orbit made up to 45x fewer retries.
Extend GitLab Duo Agent Platform into your business systems
Three developer tasks worth handing to an agent

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

Redesign how your team ships software with AI agents
A practical guide to AI-native engineering from practitioners: Find where delivery slows, decide where humans stay in control, and verify what ships.
When code is abundant
GitLab named a Leader in the 2026 Gartner® Magic Quadrant™ for DevSecOps Platforms

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 Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13
Read about this critical patch release for Community Edition and Enterprise Edition.
GitLab 19.5 released
GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8

GitLab Orbit: Find vulnerability blast radius without the manual hunt
Exploitation happens at machine speed now. Map every project, owner, and pipeline a critical CVE touches so remediation can keep up.
What happens when vulnerabilities are discovered faster than you can fix them?
Uncover the business logic vulnerabilities SAST scanners miss

Pillow CVE-2026-112900: How to find and fix it with GitLab
Upgrade to Pillow 13.0.0, then use dependency scanning, code search, and GitLab Duo Agent Platform to patch every affected Python project in your groups.
