You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By updating to semver@7 (#508) we've dropped support for NodeJS@8.
We actually haven't tagged (or published a release) in some time and it seems like we could potentially revert #508 and cut a minor before doing the upgrade.
- The conventional-changelog packages that this repository relies on heavily have dropped support for NodeJS@8 (conventional-changelog/conventional-changelog/pull/599). While the current state (v8.0.0) of _this_ library still passes tests in NodeJS@8, with reaching EOL on 12/31/2019 this seems like a change we should introduce to avoid unexpected issues/conflicts with updates in dependencies.
see #549
Yup! This ticket is probably no longer necessary. I'm going to change the title, close the ticket and add a few details for posterity.
standard-version@9officially drops support for NodeJS@8, this breaking change is listed in the changelog.
If you are using a version of standard-version > 7.1, <= 8 on NodeJS@8, you may encounter issues based on a dependency update (2f04ac8). Downgrading to 7.1.0, or using a hash before this change would likely be your best option for compatibility.
jbottigliero
changed the title
master drops support for NodeJS@8
standard-version@8 drops support for NodeJS@8 (without mention in CHANGELOG)
Sep 12, 2020
By updating to
semver@7
(#508) we've dropped support for NodeJS@8.We actually haven't tagged (or published a release) in some time and it seems like we could potentially revert #508 and cut a minor before doing the upgrade.
It's also worth mentioning that
conventional-changelog
just dropped support for NodeJS@8 onmaster
(conventional-changelog/conventional-changelog#599)The text was updated successfully, but these errors were encountered: