Please can you re-release dropping node 14 support as a breaking change?

[mattlewis92]

• I have searched for similar issues
• I am using the latest version of npm-check-updates
• I am using node >= 14.14

---

Steps to Reproduce

N/A

Current Behavior

Hey there! 👋 Installing the latest version of this package (>= 16.10.9) with engines-strict=true in a CI pipeline running node 14 fails:

We're still in the process of upgrading all our pipelines to node 16 but any that have not yet been upgraded are failing due to node 14 support getting dropped in this package and this is causing us quite a bit of pain to manually have to go in and fix everything.

Expected Behavior

When a node major support is dropped in a library it should be marked as a breaking change to prevent these kinds of problems (we currently have "npm-check-updates": "^16", in our package.json). If you could revert this commit and instead re-release it as a breaking change in v17 that would help us out tremendously so we can avoid a tonne of manual work to fix all our failing pipelines. Thank you!

[raineorshine]

Thanks for bringing this to my attention. This was not intentional. I have reverted the commit and published to v16.10.11. If the engine gets bumped, it will be released as a major version upgrade.

[raineorshine]

I'm investigating the test failures.

[mattlewis92]

Thanks for bringing this to my attention. This was not intentional. I have reverted the commit and published to v16.10.11. If the engine gets bumped, it will be released as a major version upgrade.

Thank you so much, it's very much appreciated! 🙌

[ekwoka]

Node 14 isn't supported by Node.

[raineorshine]

Closing as there is no work left to do on this issue.

See https://github.com/raineorshine/npm-check-updates/milestone/3 for issues remaining for the next major release.