fix(release): ensure tags for version match stable variant before prerelease#30047
Merged
JamesHenry merged 1 commit intomasterfrom Feb 14, 2025
Merged
fix(release): ensure tags for version match stable variant before prerelease#30047JamesHenry merged 1 commit intomasterfrom
JamesHenry merged 1 commit intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Contributor
|
View your CI Pipeline Execution ↗ for commit 02a04eb.
☁️ Nx Cloud last updated this comment at |
4 tasks
xiongemi
approved these changes
Feb 14, 2025
4 tasks
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Current Behavior
Versions with a
-suffix(prereleases) would be matched before ones without (stable) releases for the same version number.E.g.
v1.0.0-beta.1would be matched beforev1.0.0even though based on the lifecycle of development,v1.0.0would be the latest release.This is shown by the included e2e test which failed before this change, and passes after it.
Expected Behavior
The included e2e test passes.
Related Issue(s)
Fixes #27577