> 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-cms/understand-umbraco-cms/product-and-releases.md).

# Product and Releases

Track current releases, test upcoming versions, and find resources for older versions.

Use this section to follow Umbraco releases and plan your next step.

Find the latest release information, test upcoming versions, or browse older documentation.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Release Notes</td><td><a href="https://releases.umbraco.com/all-releases/">https://releases.umbraco.com/all-releases/</a></td></tr><tr><td>Legacy Documentation</td><td><a href="/umbraco-cms/understand-umbraco-cms/product-and-releases/legacy-documentation.md">Legacy Documentation</a></td></tr></tbody></table>

## In this section

* Current release information and release history.
* Guidance for testing the latest release candidate.
* Links to documentation for versions outside active support.

{% hint style="info" %}
This documentation covers supported Umbraco CMS versions. Use the legacy documentation for older versions.
{% endhint %}


---

# 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-cms/understand-umbraco-cms/product-and-releases.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.