A guide to the breaking changes in GitLab 18.0

GitLab 18.0 is poised to deliver innovative DevSecOps features while simultaneously phasing out certain deprecated functionalities. The update, scheduled to roll out in stages from April to June 2025, will affect GitLab.com, Self-Managed, and Dedicated users through various breaking changes. Significant alterations include the removal of the "Limit access from your project" setting for CI/CD job tokens, mandatory enforcement of authorized groups and projects allowlists, and enhanced security protocols for Dependency Proxy token scopes. High-impact changes focus on improving security, such as enforcing authorized allowlists for CI/CD job token access and updating Dependency Proxy authentication scopes. Medium-impact adjustments address data retention limits for vulnerabilities and require users to align container image pull policies with allowed configurations. Additionally, PostgreSQL versions 14 and 15 will no longer be supported, necessitating upgrades to version 16. There are also low-impact changes, such as the deprecation of SUSE Linux Enterprise Server 15 SP2 package support and updates to Prometheus and Terraform CI/CD templates. GitLab provides a suite of tools and resources to help users prepare for these transitions, including advanced search deprecation tools, dependency scanning support detection, and educational micro courses.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.