fix(prerelease-setup): exclude -next tags from auto-resolved upgrade versions#173
Merged
Conversation
…versions -next tags are internal builds, not release candidates. The platform RC and vCluster upgrade resolvers picked the latest pre-release, which included -next tags (e.g. 4.11.0-next.internal.1). Filter them out to match the existing exclusion pattern used elsewhere in the prerelease workflows. ENGQA-1353
sydorovdmytro
approved these changes
Jul 16, 2026
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
2 participants
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.
What
The platform RC and vCluster upgrade resolvers in
prerelease-setuppick the latest GitHub pre-release when the version input is empty.-nexttags are markedprerelease == true, so they get picked (e.g. platform4.11.0-next.internal.1in run 29025482693).Change
Add
and (.tag_name | test("-next") | not)to both resolver jq filters. Matches the existing exclusion pattern in loft-enterprisee2e-pre-release-checks.yaml.Note
Consumers pin this via the mutable tag
prerelease-setup/v1. DevOps to re-pointv1to this commit after merge.ENGQA-1353