GITLAB.COM ROLLING RELEASES: MONITOR WHAT'S LIVE NOW
GitLab maintains a continuously updated 'Available now on GitLab' page that lists what is currently deployed to GitLab.com. Use it to track features, fixes, and...
GitLab maintains a continuously updated 'Available now on GitLab' page that lists what is currently deployed to GitLab.com. Use it to track features, fixes, and deprecations that may land on SaaS ahead of monthly self-managed releases. This helps plan CI/CD, Runner, and API client changes proactively.
Catching CI/CD and API changes early reduces pipeline breakage and unplanned outages.
You can schedule Runner and dependency upgrades to match what's already live on SaaS.
-
terminal
If you use GitLab AI features, gate LLM-generated changes with required tests, SAST/DAST, and Code Owner review to ensure quality and compliance.
-
terminal
Create a canary repo that exercises AI-assisted workflows and measure impact on merge latency, pipeline duration, and defect rates after GitLab.com updates.
Legacy codebase integration strategies...
- 01.
Pin Runner versions and CI images, and run a staging pipeline on each notable GitLab.com change to detect regressions before promoting.
- 02.
Audit scripts and jobs for deprecated endpoints/features noted on the page, and add checks to fail fast when deprecations appear.
Fresh architecture paradigms...
- 01.
Start with modular .gitlab-ci.yml templates and pin tool versions to keep pipelines stable across frequent SaaS updates.
- 02.
Define AI usage policies (review gates, security scans, tracing) from day one so LLM-assisted changes integrate cleanly with CI/CD.