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?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Pinning the Release Sequence of an Application | 0 | 2101 | March 6, 2018 | |
| 500 error w/ no details while creating new release | 1 | 246 | August 12, 2023 | |
|
Sharing Support Bundles With Replicated
|
1 | 357 | November 11, 2022 | |
| Determining the release version installed on a KOTS customer | 3 | 754 | February 26, 2021 | |
| Replicated Vendor Support Paths and Processes | 0 | 1565 | July 6, 2022 |