npms-io / npms-analyzer

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

An in-range update of nsp is breaking the build 🚨 #133

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.6.3 of nsp just got published.

Branch Build failing 🚨
Dependency nsp
Current Version 2.6.2
Type dependency

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

As nsp 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/208328562)
Commits

The new version differs by 6 commits .

  • ee544f5 2.6.3
  • 1f810f5 Merge pull request #150 from nodesecurity/proxy_handling
  • 2b2385d account for empty strings in HTTPS_PROXY
  • d3f98c7 Merge pull request #131 from yannrouillard/display-cvss
  • d4abc0c Sort vulnerabilities displayed by severity in default output
  • e8acc1d Display CVSS score information in default output

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: