conventional-changelog-conventionalcommits requires Node 10?
See original GitHub issueI recently started seeing CI failures in a project that uses standard-version
, seemingly because conventional-changelog-conventionalcommits
requires Node 10 or greater. The output from Yarn is:
error conventional-changelog-conventionalcommits@1.1.1: The engine "node" is incompatible with this module. Expected version ">=10.0.0". Got "6.17.1"
The same thing happens locally if I try to run yarn upgrade standard-version
. The other packages in this repo specify >= 6.9.0
in their engines
field. Is there a reason this one requires a different version?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:9 (4 by maintainers)
Top Results From Across the Web
conventional-changelog-conventionalcommits - npm
Start using conventional-changelog-conventionalcommits in your project by running `npm i conventional-changelog-conventionalcommits`.
Read more >conventional-changelog-conventionalcommits | Yarn - Yarn
A concrete implementation of the specification described at conventionalcommits.org for automated CHANGELOG generation and version management.
Read more >Conventional-changelog NPM - npm.io
A scoped preset package such as @scope/conventional-changelog-custom-preset can be used by passing @scope/custom-preset to this option. NOTE: options ...
Read more >Automatically Generate and Release a Changelog using ...
Conventional Commits makes generating a changelog easy by creating a ... You'll need to install the standard-version npm package into your ...
Read more >Codecov
fix(deps): update dependency conventional-changelog-conventionalcommits to v5 ... !chore: Drops Node.js 10 support (end-of-life), now requires Node.js >= 12 ...
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
Same issue here using
standard-version
. I’m using yarn - here is how I how I worked around it. Inpackage.json
add this section:would also accept a patch that addresses the issue.