search

SvanBoxel / delete-merged-branch

No more manually deleting merged branches, this lovely app does it for you.
https://github.com/apps/delete-merged-branch/
ISC License
324 stars 55 forks source link

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

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

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

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.2.0

5.2.0 (2019-10-03)

Features

  • allow to configure the registry via NPM_CONFIG_REGISTRY (0126704)
Commits

The new version differs by 15 commits.

  • 0126704 feat: allow to configure the registry via NPM_CONFIG_REGISTRY
  • 07247ca chore(package): update xo to version 0.25.0
  • c255b07 chore(package): update dockerode to version 3.0.0
  • de020a6 chore: remove commitizen from our dependencies
  • c663276 fix(package): update vulnerable dependencies (#185)
  • fca8c39 chore(package): update commitizen to version 4.0.0
  • a22bc74 ci: test in node 12
  • 6b18830 chore: remove unused dev deps
  • 5698b1f chore(package): update clear-module to version 4.0.0
  • 2a45e25 fix(package): update execa to version 2.0.2
  • 9bd97fc ci: test in lowest suported node version
  • 6f40669 fix: revert to execa ^1.0.0
  • a457fdc fix: skip tarball move if config is cwd
  • 9498e21 fix(package): update execa to version 2.0.0
  • a060b91 test: write an .npmrc for package-lock related tests

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree: