Gitlab 18.0 is provided after an accurately defined choreography: braking changes that Gitlab rolls out over three times, starts windows. The first ran between 21 and 23 April. 28th to 30th April and 5th from May 5 to 5th.
Without parallel and solid appointments, medium and lower effects are upgraded for functions in categories. Gitlab stands for users of self-managed version of 18.0 gitlab According to the announcement in the blog 15 May. The managed cloud version Gitlab dedicated upgrade to Gitlab 18.0 in the period from 24 June to 29th.
High affluence change
Those people were classified as a high impact Break -up Gitlab 18.0 focuses on security. It is influenced by Gitlab 14.4 and the CI/CD job-tookons introduced with dependence proxy.
With the CI/CD job-tookons, the “border access to this project” setting is now deactivated to all new projects. In Gitlab 16.0 or more, this setting cannot be activated anymore as soon as it has been closed in a project. To control the job token access for their projects, users should use “authorized groups and projects” settings instead, which is active with Gitlab 18.0 by default.
With Gitlab 18.0, the dependence proxy for containers also receives new safety tasks. He now needs certification of both areas read_registry And write_registryThe dependence will reject proxy certification efforts that use access tokens without these two scopes.
Gitlab provides software assistants to make it easy and user. He is also involved Advanced search depression equipmentWhich tracks gitlab groups and extended in projects with api strings, indicating old tasks. In addition, you can use dependence scanning Build support detection helper Identify projects affected by three chronic dependence scanning tasks.
(Who)
