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

Update @semantic-release/npm to the latest version 🚀 #21

Merged
merged 2 commits into from
Oct 26, 2019

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Oct 26, 2019

The devDependency @semantic-release/npm was updated from 5.2.0 to 5.3.1.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


Publisher: semantic-release-bot
License: MIT

Release Notes for v5.3.1

5.3.1 (2019-10-26)

Bug Fixes

  • package: update execa to version 3.2.0 (7db019f)
  • require Node.js >=8.16 (fce3a67)
Commits

The new version differs by 4 commits.

  • 7db019f fix(package): update execa to version 3.2.0
  • fce3a67 fix: require Node.js >=8.16
  • aa34f02 test: check number of errors thrown in config verification
  • 8726eff feat: preserve local .npmrc file

See the full diff


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 🌴

@greenkeeper greenkeeper bot requested a review from Alorel as a code owner October 26, 2019 06:23
@Alorel Alorel merged commit 979f860 into master Oct 26, 2019
@Alorel Alorel deleted the greenkeeper/@semantic-release/npm-5.3.1 branch October 26, 2019 17:28
@github-actions
Copy link

🎉 This PR is included in version 2.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.

1 participant