zotoio / github-task-manager

receive github hook, notify agent, receive task results, notify github
MIT License
12 stars 4 forks source link

An in-range update of https-proxy-agent is breaking the build 🚨 #178

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency https-proxy-agent was updated from 2.2.1 to 2.2.2.

🚨 View failing branch.

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

https-proxy-agent 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 could not complete due to an error ([Details](https://travis-ci.org/zotoio/github-task-manager/builds/554912891?utm_source=github_status&utm_medium=notification)).

Release Notes for 2.2.2

Patches

  • Remove package-lock.json: c881009
  • Ignore test directory, History.md and .travis.yml when creating npm package. Fixes #42: #45
  • Update agent-base to v4.2: #50
  • Add TypeScript type definitions: #66
  • Feat(typescript): Allow input to be options or string: #68
  • Update agent-base to v4.3: #69

Credits

Huge thanks to @marco-c, @tareqhs, @ianhowe76, and @BYK for helping!

Commits

The new version differs by 7 commits.

  • e145714 2.2.2
  • 4a7ea92 Update agent-base to v4.3 (#69)
  • 13917f6 feat(typescript): Allow input to be options or string (#68)
  • c5c4ffc Add TypeScript type definitions (#66)
  • 11bc347 Update agent-base to v4.2 (#50)
  • 056c843 Ignore test directory, History.md and .travis.yml when creating npm package. Fixes #42 (#45)
  • c881009 Remove package-lock.json

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 5 years ago

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