> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/technical-details/updates.md).

# Updates

Since Braver is a cloud platform distributed on the web and via App Store (iOS and iPadOS) and Play Store (Android) application stores, we distribute updates automatically to all our users at the same time, as soon as our quality control process is completed.

In order to be notified in advance of updates, for example to prepare if it is relevant to you, we offer email notifications.

You can decide to subscribe to our update mailing list or [unsubscribe at any time](#user-content-fn-1)[^1], all on your own.

{% content-ref url="/pages/G8RYibj1DzwTd9w5BjdM" %}
[Subscription for Updates](/technical-details/updates/subscribing-to-updates.md)
{% endcontent-ref %}

Updates that represent both important new features and minor improvements will always be published on the [version tracking page](https://support.braver.net/changelog/).

### Update Frequency

* **In the case of important new features**, we will send an email notification and a [version tracking](https://support-en.braver.net/changelog/) article at least four (4) weeks in advance, referring to one or more publicly accessible guides. This will allow you to communicate relevant changes to your team as needed.
* **In the case of minor application improvements**, we will send an email notification and a [version tracking](https://support.braver.net/changelog/) article at least one (1) week in advance, referring *if relevant* to one or more publicly accessible guides. This will allow you to communicate relevant changes to your team as needed.
* **In the case of bug fixes**, we will send an email notification as soon as the update is published and available to users.

[^1]: Unsubscription is done through the same form as registration.


---

# 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://support-en.braver.net/technical-details/updates.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.