# Pinning the Release Sequence of an Application

**URL:** <https://community.replicated.com/t/pinning-the-release-sequence-of-an-application/66>\
**Category:** Supporting your customers\
**Tags:** version\
**Created:** [March 6, 2018, 8:49pm UTC](https://community.replicated.com/t/pinning-the-release-sequence-of-an-application/66 "2018-03-06T20:49:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/marc/32/7_2.png) [@marc](https://community.replicated.com/u/marc)\
**Post date:** [March 6, 2018, 8:49pm UTC](https://community.replicated.com/t/pinning-the-release-sequence-of-an-application/66/1 "2018-03-06T20:49:35Z")

</div>

## From the Vendor Console

Releases can be pinned for an individual customer via the vendor console. This takes precedence over pinning via `/etc/replicated.conf` described below.

From the customer page, a drop-down is available listing all release versions that can be pinned. Set this, and the version will be locked on the next license sync.

![Pin the application version](https://yyz2.discourse-cdn.com/flex030/images/version-pinning.png)

## From the Node

It is possible to pin the release sequence of a vendor application by creating or updating the file `/etc/replicated.conf` with property `"ReleaseSequence"` set to the numerical identifier of a release of the vendor application. This sequence number must correspond to a release that has been promoted to the channel to which the license is set.

For example:

```json
{
  "ReleaseSequence": 123
}

```

This file can be added before running the Replicated installation scripts to pin a release at install time. It is also possible to add or edit this file in a situation where Replicated is already running. In this case Replicated must be restarted for the changes to take effect. It is not possible to downgrade the vendor application using this method.