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

# Changelog

Vectary release information

{% content-ref url="/pages/zLlAga0fcXt9NwXjRPQC" %}
[May 2026](/changelog/may-2026.md)
{% endcontent-ref %}

<details>

<summary>Previous Releases</summary>

\
[February 2026](/changelog/february-2026.md)

[January 2026](/changelog/january-2026.md)

[November 2025](/changelog/november-2025.md)

[October 2025](/changelog/october-2025.md)

[September 2025](/changelog/september-2025.md)

[August 2025](/changelog/august-2025.md)

[July 2025](/changelog/july-2025.md)

[June 2025](/changelog/june-2025.md)

[May 2025](/changelog/may-2025.md)

[April 2025](/changelog/april-2025.md)

[March 2025](/changelog/march-2025.md)<br>

Until March 2025, release notes were published on [Discord](https://discord.com/channels/958000920237584444/958007687122137139).

</details>

{% hint style="success" %}

## Discord

Release notes are also published on the official [Discord server](https://discord.com/invite/kbfe4SxzMg).

\
We also encourage you to post bug reports on our Discord server (in the #bug-reports channel). It makes it easier to discuss issues in a dedicated thread and allows us to notify you directly once they’re resolved. Public threads also help us better gauge how widespread an issue is and may influence how we prioritize fixes.

Thanks so much for helping us make Vectary even better!
{% endhint %}


---

# 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://help.vectary.com/changelog.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.