> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-community-build/server-update-and-maintenance/update/determine-path.md).

# Determining the update path

Determining the path you need to take to update your version of SonarQube Community Build instance.

SonarQube Community Build uses a calendar for the versioning scheme, see [Release cycle model](/sonarqube-community-build/server-update-and-maintenance/update/release-cycle-model.md) for more details. To determine your update path, consider the following principles:

* You can update directly from one version to another if both versions are within the same year.
* You must update to the December version first to update to a next year’s version.

{% hint style="warning" %}
Due to known issues in the December 2025 release (25.12.0.117093), the January 2026 release (26.1.0.118079) may also be used as a required intermediate version when updating to later versions.
{% endhint %}

## Download links

* January 2026 version: [26.1.0.118079](https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-26.1.0.118079.zip)
* December 2025 version: [25.12.0.117093](https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-25.12.0.117093.zip)
* December 2024 version: [24.12.0.100206](https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-24.12.0.100206.zip)

## Update path examples <a href="#path-examples" id="path-examples"></a>

| **From version**            | **To version** | **Up**dat**e path**                                                    |
| --------------------------- | -------------- | ---------------------------------------------------------------------- |
| 25.10.0.x                   | 26.1.0.x       | 25.10.0.x > 26.1.0.x (direct)                                          |
| 25.3.0.x                    | 25.9.0.x       | 25.3.0.x > 25.9.0.x (direct)                                           |
| 25.9.0.x                    | 26.3.0.x       | 25.9.0.x > 25.12.0.x > 26.3.0.x (one intermediate step)                |
| 10.6                        | 25.4.0.x       | 10.6 > 24.12.0.100206 > 25.4.0.x (one intermediate step)               |
| 9.9 LTA (Community Edition) | 25.4.0.x       | 9.9 LTA > 24.12.0.100206 > 25.4.0.x (one intermediate step)            |
| 8.9 LTA (Community Edition) | 25.4.0.x       | 8.9 LTA > 9.9 LTA > 24.12.0.100206 > 25.4.0.x (two intermediate steps) |

Update path calculator

You can use our calculator to help determine your update path.

{% @sonar-embeds/upgrade-calculator fullWidth="false" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-community-build/server-update-and-maintenance/update/determine-path.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
