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

# Welcome to Akinon Release Notes

Akinon release notes provide essential information about the **current release of Akinon products, offering insights into resolved issues, new features, enhancements, and improvements**. Please review the release notes carefully as they contain up-to-date details that may not be available in other Akinon documentation.

Akinon Release Notes are structured into three main sections:

## <mark style="color:red;">**Resolved Issues​**</mark>

Resolved issues compile a list of known defects, bugs, or security issues that have been addressed in the releases. Please review the issues carefully, as they include late-breaking information.

## <mark style="color:red;">**New Features​**</mark>

New features announce and describe the latest features developed for Akinon products. Each new feature in this section provides a basic overview of a newly implemented feature.

## <mark style="color:red;">**Enhancements​**</mark>

Enhancements outline changes to already active features or functions. These changes may include updates to data fields (additions or removals), modifications in products, adjustments to API functionality, performance enhancements, and layout changes.

We encourage you to explore each release notes to stay informed about the latest developments in Akinon and see what's new in Akinon and what we're gradually rolling out.


---

# 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.akinon.com/release-notes/readme.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.