> 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-server/10.6/setup-and-upgrade/upgrade-the-server/determine-path.md).
# Determining the upgrade path
This section explains the principles to follow in order to determine if you can perform the upgrade directly or must upgrade first to intermediary version(s). This page is for SonarQube Server 10.6.
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.6 documentation. For a list of all 10.6 pages, see the [SonarQube Server 10.6 page index](https://3001318305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVhGCsZJo9Ao0Jjyhvpxl%2Fuploads%2F6hRtvTntVECC0WPvdE37%2Fsonarqube-server-10.6-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.6 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
This section explains SonarQube Server release cycle model and the principles to follow in order to determine if you can perform the upgrade directly or must upgrade first to intermediary version(s).
## SonarQube Server release cycle model
SonarQube Server follows semantic versioning. A new major or minor version is released every 2 months, and a new [Patched versions](/sonarqube-server/10.6/setup-and-upgrade/upgrade-the-server/active-versions.md) release is declared approximately every 18 to 24 months. Only the latest major release receives active support (updates and patches). During that time, the previous major release receives LTA support (security patches and fixes of blocker bugs) until the next LTA is declared.
SonarQube Server version follows the MAJOR.MINOR.PATCH model as shown below.
### Major version number
The major version number represents a series of releases with high-level objectives for the release cycle. It’s incremented with the release following an LTA version (for example, the release following 7.9 LTA was 8.0).
### Minor version number
The minor version number corresponds to incremental functional changes within a major release cycle. At the time of an LTA release, the release cycle is closed and the minor version number is frozen.
### Patch release number
The patch release number represent patches that fix blocker or critical problems.
## Upgrade path determination principles
To determine your upgrade path, consider the following principles:
* You can upgrade directly from a non-LTA version to another if there is no LTA version in your upgrade path.
* When upgrading to an LTA version, you should directly upgrade to its latest patch.
* You can upgrade from the latest LTA version to the latest non-LTA version directly.
* If you’re migrating from an earlier patch version of an LTA, you can upgrade directly to the next LTA. You don’t need to install any intermediate patch versions.
## Upgrade path examples
| **From version** | **To version** | **Upgrade path** |
| ---------------- | -------------- | --------------------------------------------------- |
| 8.9 LTA | 9.9 LTA | 8.9 LTA > 9.9 LTA (direct) |
| 7.9 LTA | 9.9 LTA | 7.9 LTA > 8.9 LTA > 9.9 LTA (one intermediary step) |
| 9.9 LTA | 10.1 | 9.9 LTA > 10.1 (direct) |
| 9.6 | 9.9 LTA | 9.6 > 9.9 LTA (direct) |
| 9.6 | 10.1 | 9.6 > 9.9 LTA > 10.1 (one intermediary step) |
For more information on LTAs, see [Patched versions](/sonarqube-server/10.6/setup-and-upgrade/upgrade-the-server/active-versions.md).
You can use our calculator to help determine your update path.
{% @sonar-embeds/upgrade-calculator fullWidth="true" %}
---
# 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-server/10.6/setup-and-upgrade/upgrade-the-server/determine-path.md?ask=&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.