https://extensionworkshop.allizom.org/documentation/publish/version-rollback/
While discussing version roll back with an AMO engineer, they noted that "the restriction for listed channel is that the only version available is the version-before-current." This limitation does not apply to unlisted versions because they do not have a current version.
To make this more concrete, say I currently have version 1.0 approved on AMO and version 2.0 is pending review. After 2.0 is approved, I want to roll back to 1.0 and release that as 2.1. At this point I have two versions: 1.0, 2.0. Since penultimate version is 1.0, I'm able to release that as 2.1.
A week later, I want to roll back to version 2.0 and release it as 2.2. At this point I have three versions: 1.0, 2.0, 2.1. Since the penultimate version is 2.0, I'm able to release that as 2.2.
https://extensionworkshop.allizom.org/documentation/publish/version-rollback/
While discussing version roll back with an AMO engineer, they noted that "the restriction for listed channel is that the only version available is the version-before-current." This limitation does not apply to unlisted versions because they do not have a current version.
To make this more concrete, say I currently have version 1.0 approved on AMO and version 2.0 is pending review. After 2.0 is approved, I want to roll back to 1.0 and release that as 2.1. At this point I have two versions: 1.0, 2.0. Since penultimate version is 1.0, I'm able to release that as 2.1.
A week later, I want to roll back to version 2.0 and release it as 2.2. At this point I have three versions: 1.0, 2.0, 2.1. Since the penultimate version is 2.0, I'm able to release that as 2.2.