> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/getting-started/release-notes.md).

# Release Notes

### Overview

Highlight is provided as a Software-as-a-Service solution and therefore is continually upgraded free of charge. We aim to release new versions every 1-2 months with interim maintenance releases as required.

Notification is given one week prior to an upgrade with detailed release notes showing all the enhancements and minor fixes in the build. The release notes will also contain links to additional information for major features. Once a new Highlight release has passed the QA testing phase it is available for partners and users to view, [contact us](/getting-started/contact-us.md) for login details.

If you would like to be notified of new releases please [contact us](/getting-started/contact-us.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://help.highlight.net/getting-started/release-notes.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.
