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

# Release environment versioning

How Release versions environments

Environments in Release are configured based on your **default** environment configuration and your **environment-specific** configuration.

Each environment in Release is associated with a specific version string, which has the format of `v{default}.{specific}`. For example, you might see that a given environment is on version `v1.2`, which means it is based on the first modification of the **default** environment and the second modification of the **specific** environment.

* The first digit refers to the version of the default environment configuration.
* The second digit refers to the version of the currently deployed environment-specific configuration.

## Find the version of a specific environment

Under each environment for a specific application, you can view the environment version listed as part of the summary, as shown in the image below.

![Find an environment version](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-b3a0bceedb0a16865088181eb85f19010d4ed91e%2Fenvironment-versions-summary.png?alt=media)

In the **Settings** tab for the application, under **Environment Configuration**, you can view the environment configuration version, as shown below.

![Environment configuration version](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-26009b962e0e48f2778247e95932533adfb490ae%2Fenvironment-versions-major.png?alt=media)

## Default configuration version

The default environment configuration's version number will increment whenever you save either the environment configuration or the default environment variables.

Once you have created an environment, this digit in the environment's version number will **not** change if you update the default environment, as it refers to the default configuration the environment-specific configuration was originally based on.

## Environment history

Release keeps a history of all changes made to the environment configuration.

In the **Settings** tab for any environment, under **History**, you can view the history of changes made to the environment configuration. This includes the date and time of the change, the user who made the change, and the version number of the configuration.

![View environment version history](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-ff4e9bbb147a0bcd3155a5040dc1f2a81e4a5af5%2Fenvironment-version-history.png?alt=media)

## Deploy the latest environment version

After changing the environment configuration, you may wish to redeploy your application. You can redeploy the application in an environment by clicking the **Deploy** dropdown in the top right corner of the environment page and then selecting **Deploy Patch**.

![Deploy new version](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-158de43e3ea638503786bfcdd81fc3bfef57bf53%2Fdeploy-patch.png?alt=media)


---

# 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.release.com/reference-documentation/release-environment-versioning.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.