> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/whats-new/release-notes.md).

# Release Notes

Stay informed about the latest and past releases of XoroERP with our comprehensive Release Notes section. We believe in continuous improvement and are committed to enhancing your ERP experience. This section provides detailed insights into the most recent updates, including new functionalities, feature enhancements, and resolved issues.

Explore the current release to take advantage of cutting-edge capabilities that boost productivity and streamline your business processes. Additionally, the archive of previous releases allows you to track the evolution of XoroERP and discover how it has evolved over time.

Stay ahead of the curve and make the most out of XoroERP's potential by leveraging the valuable information provided in our Release Notes. Stay tuned for exciting updates, as we strive to bring you the best ERP solution with every release.


---

# 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.xorosoft.com/whats-new/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.
