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

# Versions

<figure><img src="/files/3XIJYAupw5fk4sF0Kuqe" alt=""><figcaption><p>Setting a version</p></figcaption></figure>

## Overview

If you are building software that gets installed by your users, whether they are desktop, mobile or server apps, it's likely that you release them as versions. To help communicate what changes made it into which version, Released allows you to specify a version when writing a post.

## Basics

### Setting the version

If you are using the [version filter](/guide/product/changelog/staging-area.md#filter) to create your post, the version field will automatically be populated with the version used in the filter. But don't worry, you can always change the version by simply editing the version field.

To edit the version, click on the version field above the title and type in the version for this release.


---

# 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.released.so/guide/product/changelog/editor/versions.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.