# Release a Version

When you want to push changes from a branched development file to a Deployment in another Environment, such as a `STAGING` or `PRODUCTION` version of the file (see [Deployment Environments](/guides/deployment-environments.md)), the first step is to release a Version with the changes to the Deployment's associated Release Branch. 

{% hint style="info" %}
Releasing a Version only replaces the file on the target branch on your development server. To push the changes to another [Environment](/guides/deployment-environments.md), the release must be deployed (see [Deploy a Release](/guides/releases/deploy-a-release.md)).
{% endhint %}

To release a Version:

1. Go to Modules -> Development or Branches -> Versions
2. Select a Module from the Module list or a branched development file from the Branch list
3. Select a Version from the list
4. In the sidebar's Version Actions section, click Select branch... and choose the branch you want to release to (which file you want to replace)
5. Click Release
6. If the Version does not have a version number, specify one (see [Save a Version](/guides/versions/save-a-version.md#version-numbers))

## Video Tutorial

{% embed url="<https://vimeo.com/1038622683?share=copy#t=0>" %}
Releasing a Version
{% endembed %}


---

# Agent Instructions: 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:

```
GET https://docs.devin.fm/guides/versions/release-a-version.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.