Supported Develocity Versions
This page outlines the Develocity version support lifecycle, detailing the maintenance and security updates provided, the duration of support for each release, and the scope of customer support.
Support Policy Overview
Develocity Support offers customers assistance with operational guidance, troubleshooting, configuration, and upgrades. This support is delivered through two distinct categories: Product Support and Upgrade Support.
-
Product Support: This refers to the ongoing assistance provided for general usage, troubleshooting, and ensuring the stable operation of a Develocity server.
-
Upgrade Support: This specifically refers to assisting our customers in transitioning from an older version of Develocity to a newer, supported one.
Included
-
Issues affecting supported releases.
-
Guidance on installation, configuration, and performance.
-
Upgrade assistance from any version - supported and unsupported - to supported versions.
Excluded
-
Issues specific to unsupported versions (except for unblocking upgrades).
-
Problems caused by unsupported infrastructure components or topologies (e.g., unverified storage systems, custom network layers).
Each Develocity release is supported for 18 months from its general availability date. After the End-of-Life date (EOL), no product support is provided. Patch releases do not extend the EOL date of a major Develocity release. All patch releases of the same major Develocity version share the same EOL date, which is the initial EOL date of that major Develocity version.
A warning message will be displayed within Develocity for administrators as the end-of-life (EOL) date approaches, and an error message will appear once the EOL date has passed.
Documentation for supported releases is maintained and updated. After a version reaches EOL, its documentation remains accessible for reference but is no longer updated.
Version Lifecycle and EOL Schedule
Each Develocity release reaches End-of-Life (EOL) 18 months after its release date.
| Release | Release Date | EOL | Status | Documentation |
|---|---|---|---|---|
2025.4 |
2025-12-10 |
2027-06-10 |
Supported |
|
2025.3 |
2025-09-16 |
2027-03-16 |
Supported |
|
2025.2 |
2025-07-15 |
2027-01-15 |
Supported |
|
2025.1 |
2025-04-08 |
2026-10-08 |
Supported |
|
2024.3 |
2024-12-12 |
2026-06-12 |
Supported |
|
2024.2 |
2024-08-19 |
2026-04-10 |
Supported |
|
All previous releases |
- |
2026-04-10 |
Unsupported - in grace period |
Grace Period
This support policy was formally implemented on December 10, 2025. To ensure a smooth transition for existing customers, a one-time 4-month grace period is provided, which will conclude on April 10, 2026. During this time, customers with versions that became unsupported under the new policy will be given additional time and assistance to plan their upgrades.
Maintenance Updates
Maintenance updates include non-breaking improvements, dependency updates, and minor fixes. These are delivered continuously as part of new patch releases. Gradle may, at its own discretion, backport important fixes to previous major releases.
However, such backports are not guaranteed.
Security Updates
Security updates follow a separate schedule from the standard 18-month general support window. Gradle shall provide patches for security vulnerabilities, including any embedded third-party libraries, discovered in the current and previous two Major Releases based on their severity, see the table below.
| Severity | Mitigation | Resolution Time | Affected Releases |
|---|---|---|---|
CRITICAL |
7 days |
30 days |
Current + 2 previous major releases |
HIGH |
30 days |
30 days |
Current major release |
Please note that:
-
Gradle shall determine the severity of any vulnerability in its sole discretion by taking the reported CVSS score and making any necessary adjustments to account for the contextualized usages of the vulnerable Software component.
-
Customers are notified of security updates through release notes, advisories, and the release notification mailing list.
-
A dedicated page listing security advisories and CVE details for first-party CVEs is available at https://security.gradle.com.
Upgrade Guidance
Regular upgrades are strongly recommended to ensure stability, performance, and security.
Upgrade documentation: When upgrading from more than one version back, review the upgrade information for all interim versions. This information can be found in the Release Notes of each major version.
Detailed guidance for the latest release is available in the Develocity Upgrade Guide.