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

upgrade npm to v8 and allow execa to use local npm #452

Merged
merged 4 commits into from
Jan 18, 2022
Merged

upgrade npm to v8 and allow execa to use local npm #452

merged 4 commits into from
Jan 18, 2022

Conversation

travi
Copy link
Member

@travi travi commented Jan 17, 2022

No description provided.

antongolub and others added 3 commits January 17, 2022 10:02
…#445)

Co-authored-by: Matt Travi <programmer@travi.org>
BREAKING CHANGE: npm v8 dropped support for node v15, so it is no longer supported in this plugin. this should be low impact since node v15 is already EOL

Co-authored-by: Matt Travi <programmer@travi.org>
…matching the engines definition of this package

BREAKING CHANGE: the minimum required peer of `semantic-release` has been raised to match the `engines.node` requirements of this package
@travi travi changed the title fix: add upgrade npm to v8 and allow execa to use local npm Jan 17, 2022
@travi
Copy link
Member Author

travi commented Jan 18, 2022

@travi travi marked this pull request as ready for review January 18, 2022 02:36
@travi travi requested a review from a team January 18, 2022 02:36
@travi travi merged commit 2aa642c into next Jan 18, 2022
@travi travi deleted the beta branch January 18, 2022 05:20
@github-actions
Copy link

🎉 This PR is included in version 9.0.0 🎉

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants