search

continuous-software / node-nmi

Node.js SDK for NMI payment gateway.
https://nmi.com
MIT License
2 stars 2 forks source link

An in-range update of request is breaking the build 🚨 #3

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.86.0 of request was just published.

Branch Build failing 🚨
Dependency request
Current Version 2.85.0
Type dependency

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

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/continuous-software/node-nmi/builds/379199209?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 14 commits.

  • 8f2fd4d Update changelog
  • 386c7d8 2.86.0
  • 76a6e5b Merge pull request #2885 from ChALkeR/patch-1
  • db76838 Merge branch 'patch-1' of github.com:ChALkeR/request
  • fb7aeb3 Merge pull request #2942 from simov/fix-tests
  • e47ce95 Add Node v10 build target explicitly
  • 0c5db42 Skip status code 105 on Node > v10
  • d555bd7 Generate server certificates for Node > v10
  • 81f8cb5 Remove redundant code
  • db17497 Use Buffer.from and Buffer.alloc in tests
  • 0d29635 Merge pull request #2923 from gareth-robinson/cifixes
  • 3745cec Correction for Windows OS identification
  • 219a298 Alterations for failing CI tests
  • bbb3a0b 2.85.1

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:

greenkeeper[bot] commented 6 years ago

After pinning to 2.85.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Version 2.87.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 4 commits.

See the full diff

greenkeeper[bot] commented 6 years ago

Version 2.88.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 13 commits.

  • 6420240 2.88.0
  • bd22e21 fix: massive dependency upgrade, fixes all production vulnerabilities
  • 925849a Merge pull request #2996 from kwonoj/fix-uuid
  • 7b68551 fix(uuid): import versioned uuid
  • 5797963 Merge pull request #2994 from dlecocq/oauth-sign-0.9.0
  • 628ff5e Update to oauth-sign 0.9.0
  • 10987ef Merge pull request #2993 from simov/fix-header-tests
  • cd848af These are not going to fail if there is a server listening on those ports
  • a92e138 #515, #2894 Strip port suffix from Host header if the protocol is known. (#2904)
  • 45ffc4b Improve AWS SigV4 support. (#2791)
  • a121270 Merge pull request #2977 from simov/update-cert
  • bd16414 Update test certificates
  • 536f0e7 2.87.1

See the full diff