Avoid selecting Helm beta and alpha releases #21293
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was just a Helm release of v4.0.0-alpha.1 and looking at v3.0.0-beta.5 we can expect the v4 releases to also do betas. These all should be skipped just like the release candidates (rc).
|
Opened matching change in microsoft/azure-pipelines-tasks-common-packages#489 for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Ref: #21287
There was just a Helm release of v4.0.0-alpha.1 and looking at v3.0.0-beta.5 we can expect the v4 releases to also do betas. These all should be skipped just like the release candidates (rc).
The bug report is for HelmInstaller@1, which needs to be patched in
microsoft/azure-pipelines-tasks-common-packagesrepository. However, the older HelmInstaller@0 task's auto-selection logic is also affected in the same exact way.Task Name
HelmInstaller@0
Description
Use
semverpackage's pre-release parsing, for easily identifying release candidates, betas and alphas. And then skip those specific pre-releases.Risk Assessment (Low / Medium / High)
Low. Semver specification is clear on how versions should be named, and Helm has been consistently applying those principles.
Change Behind Feature Flag (Yes / No)
No. This change mitigates an on-going bug, to restore Helm v3 as
latestuntil a generally available v4 is published.Tech Design / Approach
N/A.
Documentation Changes Required (Yes/No)
No. Users expect
latestto be a stable release already.Unit Tests Added or Updated (Yes / No)
No.
Additional Testing Performed
Manual confirmation of logic.
Logging Added/Updated (Yes/No)
No logging changes.
Telemetry Added/Updated (Yes/No)
No telemetry changes.
Rollback Scenario and Process (Yes/No)
No rollback scenario. If beta or alpha releases are to be considered stable, then the overall communication to users should be modified.
Dependency Impact Assessed and Regression Tested (Yes/No)
Yes.
Checklist