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

Unsupported engine during npm update #466

Closed
dotCipher opened this issue Mar 16, 2022 · 2 comments · Fixed by #468
Closed

Unsupported engine during npm update #466

dotCipher opened this issue Mar 16, 2022 · 2 comments · Fixed by #468
Labels

Comments

@dotCipher
Copy link

When running npm update on a repo with this plugin it fails with the following error:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'gradle-semantic-release-plugin@1.6.7',
npm WARN EBADENGINE   required: { node: '^16.14.0' },
npm WARN EBADENGINE   current: { node: 'v17.6.0', npm: '8.5.1' }
npm WARN EBADENGINE }

Does this not work with node v17.6.0 ?

@KengoTODA
Copy link
Owner

Just not sure, because I haven't tested this product with non-LTS version.
It probably works, but not been verified yet.

KengoTODA added a commit that referenced this issue Mar 16, 2022
KengoTODA added a commit that referenced this issue Mar 16, 2022
KengoTODA pushed a commit that referenced this issue Mar 16, 2022
## [1.6.8](v1.6.7...v1.6.8) (2022-03-16)

### Bug Fixes

* support NodeJS v14 explicitly ([5a48e2b](5a48e2b)), closes [/github.com/semantic-release/semantic-release/blob/2b94bb4e0967c705ab92deace342f9fecb02909d/package.json#L73](https://github.com//github.com/semantic-release/semantic-release/blob/2b94bb4e0967c705ab92deace342f9fecb02909d/package.json/issues/L73)
* support NodeJS v17 explicitly ([979205c](979205c)), closes [#466](#466)
@KengoTODA
Copy link
Owner

🎉 This issue has been resolved in version 1.6.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

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 a pull request may close this issue.

2 participants