> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-deploy/17.latest/upgrading/upgrades.md).

# Upgrading Umbraco Deploy

How to upgrade Umbraco Deploy

As with all Umbraco products, it is always recommended to run the latest version of Umbraco Deploy.

On the Umbraco Deploy page in the [Packages page](https://our.umbraco.com/packages/developer-tools/umbraco-deploy/) you can see what the latest version is, as well as read the changelog.

Umbraco Deploy can be upgraded via NuGet.

Open the **Package Console** in Visual Studio and type:

`Update-Package Umbraco.Deploy.OnPrem`

You will be prompted to overwrite files. You should choose **"No to All"** by pressing **"L"** .

You can open the **NuGet Package Manager** and select the **Updates** pane to get a list of available updates. Choose the package called **Umbraco.Deploy.OnPrem** and click update. This will run through all the files and make sure you have the latest changes while leaving the files you have updated.

## [Version Specific Upgrade Details](/umbraco-deploy/17.latest/upgrading/version-specific.md)

Contains version-specific documentation for when upgrading to new major versions of Umbraco Deploy.


---

# 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.umbraco.com/umbraco-deploy/17.latest/upgrading/upgrades.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.