Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Bump semver from 6.3.0 to 7.0.0" #437

Merged
merged 1 commit into from
Jan 15, 2020
Merged

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Jan 15, 2020

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 for semver@7.0.0 stated:

  • Refactor module into separate files for better tree-shaking
  • Drop support for very old node versions, use const/let, => functions, and classes.

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 way yarn works by default, this change in engines is actually a breaking change for yarn users (unless they specify the --ignore-engines flag).

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 for `semver@7.0.0` stated:

* Refactor module into separate files for better tree-shaking
* Drop support for very old node versions, use const/let, => functions,
  and classes.

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](npm/node-semver@d61f828)).
Unfortunately, due to the way `yarn` works by default, this change in
`engines` is actually a breaking change for `yarn` users (unless they
specify the `--ignore-engines` flag).
@rwjblue rwjblue added the bug label Jan 15, 2020
@rwjblue rwjblue merged commit d9cdf84 into master Jan 15, 2020
@rwjblue rwjblue deleted the revert-semver-update branch January 15, 2020 16:15
@rwjblue
Copy link
Member Author

rwjblue commented Jan 15, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants