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 passport is breaking the build 🚨 #185

Open
greenkeeper bot opened this issue Dec 9, 2019 · 1 comment
Open

An in-range update of passport is breaking the build 🚨 #185

greenkeeper bot opened this issue Dec 9, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 9, 2019

The dependency passport was updated from 0.4.0 to 0.4.1.

🚨 View failing branch.

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

passport 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 is in progress (Details).
  • continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • SockRPG: Build failed (Details).

Commits

The new version differs by 26 commits.

  • 42ff63c 0.4.1
  • 0362042 Update README and LICENSE with copyright date.
  • e15ee93 Remove node 0.6, add node 9-13 on Travis CI.
  • 08f57c2 Merge pull request #749 from jaredhanson/ayZagen-feat/strategy-as-object
  • 5c288ae Move test.
  • 380b5c8 Stylistic edits.
  • 4cce2f2 feat: ability to pass strategy object to authenticate
  • 1c8ede3 Update README.
  • dc16cba Add FUNDING.
  • 882d65e Update README.
  • 8ea4f24 Update GitHub templates.
  • 2327a36 Update sponsors.
  • e458838 Update README.
  • d784e17 Add GitHub templates.
  • 0a66012 Re-enable node 0.6 on Travis CI.

There are 26 commits in total.

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 Dec 9, 2019

After pinning to 0.4.0 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