Avoid selecting Helm beta and alpha releases#489
Open
sigv wants to merge 2 commits intomicrosoft:mainfrom
Open
Avoid selecting Helm beta and alpha releases#489sigv wants to merge 2 commits intomicrosoft:mainfrom
sigv wants to merge 2 commits intomicrosoft:mainfrom
Conversation
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).
3 tasks
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
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.
Description
Ref: microsoft/azure-pipelines-tasks#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).
Use
semverpackage's pre-release parsing, for easily identifying release candidates, betas and alphas. And then skip those specific pre-releases.Package Name
azure-pipelines-tasks-kubernetes-common
Risk Assessment (Low / Medium / High)
Low. Semver specification is clear on how versions should be named, and Helm has been consistently applying those principles.
Unit Tests Added or Updated
Additional Testing Performed
Manual confirmation of logic.
Documentation Changes Required (Yes / No)
No. Users expect
latestto be a stable release already.Dependencies
No dependency changes.
Checklist