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

# Release Notes

## Release Notes

Product changes, in chronological order. Focus on impact and action.

### What to record here

* **Added:** new features and new capabilities.
* **Improved:** performance, UX, quality, limits, coverage.
* **Fixed:** bugs and regressions.
* **Breaking change (if any):** what broke + how to migrate.

{% hint style="info" %}
A good release note answers: **what changed**, **for whom**, **what impact**, **what to do now**.
{% endhint %}

### Template (copy and paste)

<details>

<summary>Update template</summary>

{% code title="Template" %}

```
{% update date="YYYY-MM-DD" %}
# YYYY-MM-DD — Short release title

## Added
- _(what was added + for whom)_

## Improved
- _(what improved + measurable impact, if any)_

## Fixed
- _(what was fixed + context of the problem)_

## Breaking changes (if any)
- _(what changed)_
  - **How to migrate:** _(short steps)_
  - **Who is affected:** _(e.g.: production projects / only new ones)_
{% endupdate %}
```

{% endcode %}

</details>

{% updates format="full" %}
{% update date="2026-02-21" %}

## 2026-02-21 — (fill in the release title)

### Added

* *(fill in)*

### Improved

* *(fill in)*

### Fixed

* *(fill in)*

### Breaking changes (if any)

* *(fill in)*

{% hint style="warning" %}
If there is a change that affects production, put it at the top and include “How to migrate”.
{% endhint %}
{% endupdate %}
{% endupdates %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.madrix.dev/release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.