# Releases

## Branch Deploys

In an effort to keep everything as automated as possible, we have two main protected branches that get automatically deployed in most of our projects:

| `develop`                         | `master`                             |
| --------------------------------- | ------------------------------------ |
| Deploys to a staging environment. | Deploys to a production environment. |

{% hint style="info" %}
Pull requests also get deploy previews when applicable.
{% endhint %}

## Version Bumps & Releasing

When a task is finished, it gets merged to `develop`. When `develop` is tested and ready to become a production release, the following process takes place:

1. We run [standard-version](https://github.com/conventional-changelog/standard-version) on `develop` and take advantage of our [Git](/contribution-guidelines/code-style-and-guidelines/git.md) style conventions to automatically create or update a changelog and bump the version number following [semver](https://semver.org) guidelines.
2. We push and submit a pull request to `master`.
3. We conduct one final review before merging and letting CI/CD take care of the rest.


---

# 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.kleros.io/contribution-guidelines/general-dev.-workflow/releases.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.