Fix action for upgrading from pre-release to stable version #15898
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #15891
Occurred changes and/or fixed issues
Added an extra check for the case where you upgrade from a pre-release to a stable version.
Technical notes summary
isUpgradeFromPreToStablefunction toshell/utils/version.jsto detect upgrades from pre-release to stable versions.Areas or cases that should be tested
As described in the issue's description install an older pre-release version of a chart(e.g. Kubewarden), then go to the chart's detail page and select versions above and below it and check the action button to make sure it display the correct wording, then by clicking on the action button go to the install wizard page to check the correct wording there too.
Areas which could experience regressions
108.0.0+up0.25.0-rc.4(e.g.Rancher Turtles - the Cluster API Extension) those should be tested too.Screenshot/Video
Checklist
Admin,Standard UserandUser Base