Documentation Versioning
Develocity documentation is published as one set per major release, covering every minor version of that release.
This page explains the version scheme, how to find the documentation that matches your server, and how feature availability is marked.
Version Numbers
Develocity uses a YEAR.MAJOR.MINOR version scheme.
YEAR.MAJOR-
A major release that introduces new features and significant improvements, for example
2026.2. YEAR.MAJOR.MINOR-
An update to a major release, for example
2026.2.3. Minor releases mostly contain bug fixes and may add new features. Minor releases do not introduce breaking changes.
Documentation targets the latest minor version of each major release. Content may not apply to earlier minor versions of the same release.
Finding the Right Documentation
Use the version selector at the top of the page to switch between major releases.
The selector lists each release by its YEAR.MAJOR number, such as 2026.2 or 2026.1.
Selecting a release loads the documentation set for that release.
To match the documentation to your environment, read the YEAR.MAJOR portion of your server version.
A server running 2026.2.3 uses the 2026.2 documentation set.
For the specific fixes and features in each minor version, see the Develocity release notes. For releases before 2025.3, see Legacy Documentation. For the support lifecycle of each release, see Supported Develocity Versions.
Feature Availability
Develocity sometimes releases a new feature in beta before it is fully complete. The documentation marks these features so that you know their status in the current release.
- Beta
-
A new feature that you can try out before it is finished. The feature and its documentation may still change while it is in beta. If you use a beta feature in production, be aware that it may change in a later release.
When a feature is removed or replaced, the documentation marks it as deprecated and points to the recommended alternative.
Component Versions
Beyond the Develocity server, the ecosystem includes independently versioned components, such as the Gradle plugin, Maven extension, Edge Node, Artifact Cache CLI, and Develocity Reporting and Visualization. Each component follows its own version scheme and release cadence, separate from the server version.
For the compatibility of each component with a given Develocity server version, see Version Compatibility.