GitLab updates
At adista, we apply two types of updates:
- Monthly updates
- Security updates
Monthly updates
To ensure the stability and security of your GitLab instance, we operate a monthly update policy.
Updates are applied on the fourth Tuesday of each month, from 9h30 p.m.
GitLab releases a new minor version on the third Tuesday of every month. As soon as it is available, our team installs it internally, and it undergoes a series of tests for a week. This period also allows us to integrate any fixes released by GitLab in the meantime.
At the end of this validation phase, the minor version, along with any bug fixes released in the meantime, are deployed to your platform during the monthly maintenance window. This approach aims to minimize the risks associated this introducing new features or unforeseen regressions.
Upcoming GitLab Releases
| Version | Release Date | Deployment Date by Adista |
|---|---|---|
| 18.4 | September 19, 2025 | September 25, 2025 |
| 18.5 | October 16, 2025 | October 23, 2025 |
| 18.6 | November 20, 2025 | November 27, 2025 |
| 18.7 | December 18, 2025 | January 5, 2026 (due to the end-of-year holidays) |
| 18.8 | January 15, 2026 | January 22, 2026 |
| 18.9 | February 19, 2026 | February 26, 2026 |
| 18.10 | March 19, 2026 | March 26, 2026 |
| 18.11 | April 16, 2026 | April 23, 2026 |
| 19.0 | May 21, 2026 | No update deployed |
| 19.1 | June 18, 2026 | June 25, 2026 |
| 19.2 | July 16, 2026 | July 23, 2026 |
| 19.3 | August 20, 2026 | August 27, 2026 |
Specific features of major version deployment
Gitlab releases a new major version every year, in May. These versions add significant changes and deprecations, as well as potential bugs.
As a precaution, we do not deploy this version immediately, but rather wait until the following month, when the next patch release (containing initial bug fixes) is released, before proceeding with the installation.
GitLab provides support for the thress most recent minor versions: N, N-1 and N-2. Therefore, delaying the installation of a major version by one month has no impact on the security of your instance. Security patches will continue to be released for version N-!, which is then installed on your instance, thus ensuring that your environment remains secure.
Security updates
There is no need to open a ticket when GitLab notifies you that an update is available. Out tems are already informed of the patch release and are handling its analysis, and will deploy it according to established procedures.
When a security patch is released, a pop-up message appears on your GitLab interface, prompting you to update as soon as possible. We are already aware of the availability of the patch's availability, and we are conducting a thorough analysis of its potential impact on your infrastructure.
If our team determines that your system is affected by a critical vulnerability, you will be notified immediately. In this case, we will schedule an exceptional update as soon as possible.
However, if we determine that your system is not affected, out team will not contact your unnecessarily, and your GitLab instance will be updated at the end of the month, as part of our regular monthly maintenance schedule. This approach aims to ensure optimal security for your platform.
If you have any questions about your subscription or the GitLab solution offered by adista, please contact uour dedicated sales representative, who will be happy to assis you.
Review the release notes
To stay up to date with GitLab's developments adn learn about the details of new releases, you can consult the official release notes.
Anticipate breaking changes
Some updates may introduce major changes and deprecations. To anticipate these changes and adapt your workflows accordingly, we recommand that you regurlarly review the dedicated documentation.