Why does gitlab.com/help report that it's a prerelease version?

General
1

When I go to Help · GitLab, it reports that it’s version GitLab Enterprise Edition 17.5.0-pre 66f780ac568. We’d rather use only GA versions, not prereleases. How do you configure that, or is it even configurable?

2

GitLab.com SaaS is a rolling release, using continuous delivery including development, staging and canary deployments. Deployments and Releases | The GitLab Handbook

Using a specific version of GitLab is possible on GitLab Dedicated, or on a self-managed instance.

2 Likes
3

So, are you saying that we’re getting a canary deployment of the prerelease version and we can’t avoid it?

4

As @dnsmichi said, if you want a GA release, run your own Gitlab server or pay for Gitlab dedicated. Gitlab and their employees manage and maintain the version of gitlab.com so you have no control of what version they run nor can you choose. They decide. As long as gitlab.com works, it shouldn’t really matter what version it is. If gitlab.com stops working or has issues, the Gitlab team fix it as they are responsible for it. At this point, it’s for you to decide whether that fits your need or not and change to dedicated/run your own server of which you have control over.

This is no different for Github either or any other Git-based hosting service that are managed and maintained by the people who own it. They choose what software release it is.

2 Likes
5

GitLab.com SaaS gets a tested version deployed, after passing all stages. The exact time windows for release deployments and also product deployment freezes are documented in the handbook, see URL above.

Users cannot influence the deployed versions, as GitLab.com is operated by the GitLab infrastructure team as admins, and runs as multi-tenant SaaS. If you require a specific release version, a single tenant solution with GitLab Dedicated can be an option.

2 Likes
6

Ok thanks

2 Likes