Last Call

AI on duty

Get the digest

Calendar · By vendor

Everything GitLab is sunsetting

4 things GitLab has scheduled to be taken away — soonest first. Each links to GitLab’s own announcement.

Feature →28 weeks

GitLab GitLab Design Management — the feature that lets users attach design assets such as wireframes and mockups to issues — is deprecated and begins removal in GitLab 20.0: new uploads stop, and existing designs become read-only until GitLab 21.0

Feature →28 weeks

GitLab GitLab compliance pipelines — the feature that forces compliance- or security-related CI jobs to run in projects assigned a compliance framework label — are deprecated and will be removed in GitLab 20.0. The replacement is the pipeline execution policy type.

Feature →28 weeks

GitLab GitLab is removing the Dependency Proxy for packages — the feature that proxies and caches packages pulled from upstream Maven registries — in GitLab 20.0 (20 May 2027). It is replaced by the Maven virtual registry, and affected projects must repoint their package-manager configuration from the Dependency Proxy for packages endpoints to the Maven virtual registry.

Feature · signalled ·not announced

GitLab The official GitLab Helm chart and GitLab Operator are dropping their bundled Ingress controllers — NGINX Ingress, HAProxy and Traefik — with full removal planned for GitLab 20.0. Since 19.0 the chart defaults to the Kubernetes Gateway API with a bundled Envoy Gateway, and the bundled controllers are deprecated and disabled by default. GitLab has not announced a specific calendar date, only the 20.0 milestone.

Other vendors on the board