Revert "Bump semver from 6.3.0 to 7.0.0" #437
Merged
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.
This reverts commit 1c62ef6.
tldr;
semver@7.x
arguably includes breaking changes in a minor release (from 7.0.0 to 7.1.0), and we cannot update to 7.x until ember-cli-htmlbars drops Node 8 support.At the time the
semver@7.0.0
version bump (from 1c62ef6) landed the CHANGELOG.md forsemver@7.0.0
stated:The verbiage here is obviously imprecise, and when merging (and releasing) I misinterpretted "very old node versions" as being versions older than Node 4.0.0 (in other words, versions that didn't support the features stated immediately following). Unfortunately, semver changed their
engines
version after 7.0.0 was released (included in the 7.1.0 release) to only allow Node 10 or higher (see here). Unfortunately, due to the wayyarn
works by default, this change inengines
is actually a breaking change foryarn
users (unless they specify the--ignore-engines
flag).