---
component: ROOT
version: "2026.3"
slug: ROOT/miscellaneous/versioning
canonical_url: "https://docs.develocity.ai/2026.3/miscellaneous/versioning/"
title: "Documentation Versioning"
description: "How Develocity documentation maps to release versions, how to find the docs that match your server, and how feature availability is marked."
keywords:
  - "develocity versioning"
  - "upgrade"
status: current
---

<!-- llms-index: https://docs.develocity.ai/llms.txt -->

# Documentation Versioning

<a id="preamble"></a>

Develocity publishes one documentation 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 the documentation marks feature availability.

<a id="version-numbers"></a>

## 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.3`.

**YEAR.MAJOR.MINOR** — An update to a major release, for example `2026.3.0`. Minor releases contain bug fixes, and some add new features. Minor releases do not introduce breaking changes.

Documentation targets the latest minor version of each major release. Content does not always apply to earlier minor versions of the same release.

<a id="finding-the-right-documentation"></a>

## 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.3` or `2026.2`. 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.3.0` uses the `2026.3` documentation set.

For the specific fixes and features in each minor version, see the [Develocity release notes](https://develocity.ai/releases/). For releases before 2025.3, see [Legacy Documentation](https://docs.develocity.ai/2026.3/miscellaneous/legacy-docs/). For the support lifecycle of each release, see [Supported Develocity Versions](https://docs.develocity.ai/2026.3/miscellaneous/support-policy/).

<a id="feature-availability"></a>

## 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 can still change while it is in Beta.

When a feature is removed or replaced, the documentation marks it as deprecated and points to the recommended alternative.

<a id="component-versions"></a>

## Component Versions

The Develocity ecosystem also 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 every component and how to track its releases, see [Tracking Component Releases](https://docs.develocity.ai/2026.3/operations/tracking-component-releases/). For the compatibility of each component with a given Develocity server version, see [Version Compatibility](https://docs.develocity.ai/2026.3/miscellaneous/compatibility/).