It looks like node 8 was dropped in a patch release
See original GitHub issuehttps://github.com/conventional-changelog/conventional-changelog/pull/599
Now getting the following in CI error conventional-recommended-bump@6.0.9: The engine "node" is incompatible with this module. Expected version ">=10". Got "8.17.0"
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Update Now! Node.js 8 is Not Supported from 2020.
It... cycle will expire on December 31, 2019 – which means that Node 8 won't get any more updates, bug fixes or security...
Read more >Drop Node 4 support (and Node 6 and Node 8) #3919 - GitHub
The official support for Node 4 is ending soon (April 2018) and from time to time we have quite a few issues like...
Read more >Upgrading Node.js to latest version - Stack Overflow
Just go to nodejs.org and use the latest installer. · 2. I had to run choco install nodejs. · Make sure to run...
Read more >LostGrid to no longer support older versions of Node
Version 8 isn't quite ready yet and I'm going hold off releasing it until December when Node support for v0. 12 ends.
Read more >Drop of Node.js 12 support and deprecation of Node.js 14 ...
To be clear, we do support Node.js LTS v14 as deprecated, however that does not mean we support all its old minor releases....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any chance of getting a patch release reverting this breaking change?
To make standard-version 7.x work in node 8, we had to use yarn resolutions to pin the following. Going any newer in the semver range defined by the calling package would try to use a version with the engine error.