How to use Ruby 3.1 as the default container image on GitLab SaaS Runners on Linux

On January 12, 2023, GitLab will update the default container image used on GitLab SaaS Runners on Linux from Ruby 2.5, which has reached its end of life, to Ruby 3.1, with no impact expected for those who have specified a custom container image in their CI/CD job configurations. Users can verify the container image used by checking the CI job log, and those without a specified image will automatically transition to Ruby 3.1. To proactively address any potential compatibility issues, users are advised to configure their jobs to run in a Ruby 3.1 container by updating their .gitlab-ci.yml files. Additionally, GitLab plans to implement a new maintenance process for container images to ensure they contain the latest security updates, though users are cautioned that the details of future products, features, and timelines are subject to change at the discretion of GitLab Inc.

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.