Version track¶
In order to give you the most control over your GitLab version, we've introduced a setting called Version Track. With this setting, you can choose whether you prefer new features, or would rather minimize the risk of updating.
You can change this setting in our Control Panel under your GitLab instance settings. Currently, we offer 3 options: fast, stable & slow. The version tracks correspond to minor versions of GitLab. You can find more information about version track management below. Please note that it is not possible to downgrade a version as this is not supported by GitLab.
Supported versions¶
GitLab uses Semantic Versioning, this means their release numbers follow the format: major.minor.patch. For stability and reliability of your GitLab instance, we wait for the first patch (major.minor.1) to be released before we install that minor version.
Please note that we do not support control over patch versions. These releases often contain security fixes, and are therefor mandatory in accordance with our security policies. We rely on GitLab's release policy. If you want to stay up-to-date about releases, we recommend you follow their release blog.
Version track management¶
In line with GitLab's release policy, we offer 3 version tracks: fast, stable & slow. The differences are:
- fast: The latest supported minor version
- stable: The previous supported minor version
- slow: The supported minor version behind stable
The default version track setting is stable. To manage the version track, visit the settings of your instance. After you change the version track, the instance will upgrade during the configured maintenance window. Upgrading GitLab might come with considerable downtime.
As stated before, it is not possible to downgrade the version track because GitLab doesn't support downgrading.