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

# Changelogs

Where to find release notes for every Waro Studios script.

We don't keep a copy of every release note on this site. During early access (0.x), scripts change often, and one place for release notes is easier to follow.

## Where release notes live

| Where                                   | What you'll find                                                                   |
| --------------------------------------- | ---------------------------------------------------------------------------------- |
| **Discord: changelog channel**          | Every release, posted when it goes out. Follow the channel to get notified.        |
| **`CHANGELOG.md` in the script folder** | The full history of that script, version by version. It comes with every download. |
| **The script's page here**              | How the current version works. We update the page when options or commands change. |

## Reading a changelog

Each version has a date and sections like these:

* **Added:** new features or options.
* **Changed:** something works differently. Check your config.
* **Fixed:** bugs that were fixed.
* **Removed:** options or features that were taken out.

{% hint style="warning" %}
Before you update, always look for **Changed** and **Removed**. They tell you if you need to edit your config. See [Updating](/getting-started/updating.md).
{% 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://docs.warostudios.com/help/changelogs.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.