Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Jul 6, 2019 · 1 comment
Open

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

greenkeeper bot opened this issue Jul 6, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jul 6, 2019

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

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. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 6, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants