Description

With the current release process, before a new release is published the version and appVersion in charts/rancher-turtles-providers/Chart.yaml must be manually updated to match the coming release.

This configuration allows us to use the existing rancher/prime-charts automation for creating new versions of prime-only charts.

However, it poses the problem of forcing us to change the state of the repository after validation on a release candidate is performed, which effectively means that we end up creating a stable release that doesn't correspond to the same version of the code (different commit hash).

For example:

• rancher-turtles and rancher-turtles-providers v0.26.0-rc.1 is published for validation.
• Validation is successful and we're now ready to create a stable v0.26.0.
• Before we un-RC, we must update rancher-turtles-providers Chart.yaml to set v0.26.0. At this point we add commits on top of the validated revision.
• Without the above change we cannot release a new rancher-turtles-providers chart.

This can get worse if, during the time between RC creation and un-RC, new changes are merged to the release branch. In this case the branch has diverged from the original state of the QA-validated RC.

Definition of Done

We should be able to un-RC a version of Turtles maintaining the same code revision.