npms-io / npms-analyzer

The analyzer behind https://npms.io
MIT License
319 stars 38 forks source link

An in-range update of normalize-package-data is breaking the build 🚨 #135

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.3.6 of normalize-package-data just got published.

Branch Build failing 🚨
Dependency normalize-package-data
Current Version 2.3.5
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As normalize-package-data is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:


Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/npms-io/npms-analyzer/builds/208780999)
Commits

The new version differs by 6 commits .

  • f6c3706 2.3.6
  • 2ccbe68 remove trailing whitespace & add final newlines (#76)
  • 5f42e5d Couple of README usage example fixes (#78)
  • 3ebec8d fix typos in readme (#79)
  • 89bf8d6 test/normalize should not normally write to stderr (#80)
  • c98337f Fix documentation (#82)

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree: