fix: advance beta line after stable releases#48
Open
itzptk wants to merge 1 commit into
Open
Conversation
Use the latest stable tag even when package.json still contains a prerelease version, so scheduled beta releases move to the next patch line after a stable release exists. Add release-versioning regression coverage for caught-up and no-stable-tag prerelease cases.
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
1 participant
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 #14
Verification
git diff --checknpm run test:node -- release-versioning— 1 file / 4 tests passednpm run test:all— Angular 114 files / 252 tests passed; Node 15 files / 119 tests passednpm run build— Angular production build and Electron tsup build succeededReview