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

# Release notes

We launch a lot of new stuff

On this page you can find our release notes. These are only available for event and company moderators.

Each time new features are added to the platform they will be posted in these release notes. If there are new release notes you have not read yet, a pink bell icon will be shown on the top right corner of the moderator pages.

<figure><img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-52126d25fad7808e1da59d8291b37acb4ca774f9%2Freleasenotes%20bell.jpg?alt=media" alt="" width="35"><figcaption><p>There are unread releasenotes</p></figcaption></figure>

Click this bell icon to find the newest release notes.

### Too busy to check the website?

You can receive a weekly email summarizing our latest platform updates. Simply head to the Release notes page, click "Subscribe," and every Tuesday we'll email you the highlights from the previous week. You can unsubscribe anytime, but we encourage you to stay in the loop so you're always up to date with our newest updates and features.


---

# 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.eventication.com/event/misc/releasenotes.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.
