chore(version): update tests to reflect new behavior of semver #3785
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
Updates the publish integration tests to reflect the bug that was fixed in semver - npm/node-semver#533
Motivation and Context
Semver used to consider the difference between "v1.0.0" and "v1.0.0-alpha.0" to be a prerelease. Now it considers that a major version bump. This change means that Lerna will now consider "v1.0.0-alpha.0" to "v1.0.0" a major version bump and therefore breaking change, which triggers the release of all other packages when in fixed mode.
I believe that Lerna's new behavior (due to this semver change) makes sense and is consistent with Lerna's existing pattern of publishing all packages when a breaking change is made.
Types of changes
Checklist: