# Release Sequence Workaround

**URL:** <https://community.replicated.com/t/release-sequence-workaround/861>\
**Category:** Supporting your customers\
**Created:** [July 11, 2022, 4:00pm UTC](https://community.replicated.com/t/release-sequence-workaround/861 "2022-07-11T16:00:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Aruj](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/alexander_aruj/32/500_2.png) [@Alexander\_Aruj](https://community.replicated.com/u/Alexander_Aruj)\
**Post date:** [July 11, 2022, 4:00pm UTC](https://community.replicated.com/t/release-sequence-workaround/861/1 "2022-07-11T16:00:55Z")

</div>

When a release like 2.12.1.1 has been pushed to Replicated for testing AFTER 2.12.2.0 a customer would not be able to upgrade from say 2.12.1.1 to 2.12.2.0 as far as I know.

Is there a workaround / feature request to accomodate this case?