> 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/server-update-and-maintenance/update/roadmap.md).

# Overview

The section lists the steps you have to perform to update your SonarQube Server installation. This page is for SonarQube Server 2026.5.

{% hint style="warning" %}
Installing SonarQube Server from the ZIP file is deprecated. It's still supported, but support will be removed in a future release, so if you run a ZIP installation, consider moving to the [Docker image](https://hub.docker.com/_/sonarqube) or the [Helm chart](https://artifacthub.io/packages/helm/sonarqube/sonarqube) as part of your next update. See the [deprecation policy](/sonarqube-server/server-update-and-maintenance/maintenance/deprecations/deprecation-policy.md) for details, and [Moving from a ZIP file installation to a Docker installation](/sonarqube-server/server-update-and-maintenance/update/other-procedures.md#from-zip-to-docker) for the procedure.

The agentic features run as containers, so they have no ZIP equivalent. You can keep SonarQube Server on the ZIP file and deploy their containers alongside it. See [Deploying AI agents](/sonarqube-server/server-installation/ai-agents.md).
{% endhint %}

## Reasons to update immediately <a href="#reasons-to-upgrade-immediately" id="reasons-to-upgrade-immediately"></a>

In SonarQube Server, you need to perform an update in the following situations:

1. If you are on a version of SonarQube Server that is no longer active.
2. If you are on the latest version of SonarQube Server and there is a new update available.
3. If you are on the latest version or Long-Term-Active (LTA) for which there is a new patch version available (security and bug fixes).

## Update steps <a href="#upgrade-steps" id="upgrade-steps"></a>

Follow these steps to perform an update of your SonarQube Server:

1. Read [Release cycle model](/sonarqube-server/server-update-and-maintenance/update/release-cycle-model.md).
2. [Determining the update path](/sonarqube-server/server-update-and-maintenance/update/determine-path.md).
3. Read the [Release notes](/sonarqube-server/server-update-and-maintenance/release-notes.md#upgrade-notes) between the SonarQube versions.
4. [Pre-update steps](/sonarqube-server/server-update-and-maintenance/update/pre-update-steps.md).
5. Back up the SonarQube Server database.
6. [Performing the update](/sonarqube-server/server-update-and-maintenance/update/update.md).
7. [Post-update steps](/sonarqube-server/server-update-and-maintenance/update/post-update-steps.md).

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Upgrading from SonarQube Community Build](/sonarqube-server/server-update-and-maintenance/update/updating-from-sonarqube-community-build.md)
* [Moving to another SonarQube Server edition](/sonarqube-server/server-update-and-maintenance/update/moving-to-another-edition.md)
* [Other migration-related tasks](/sonarqube-server/server-update-and-maintenance/update/other-procedures.md)


---

# 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/server-update-and-maintenance/update/roadmap.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.