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 underscore is breaking the build 🚨 #519

Open
greenkeeper bot opened this issue Jan 6, 2020 · 1 comment
Open

An in-range update of underscore is breaking the build 🚨 #519

greenkeeper bot opened this issue Jan 6, 2020 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 6, 2020

The dependency underscore was updated from 1.9.1 to 1.9.2.

🚨 View failing branch.

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

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

Commits

The new version differs by 12 commits.

  • 853dd76 Underscore.js v1.9.2
  • 3c6d93b Merge pull request #2816 from Margen67/https
  • 46888bf Make links HTTPS
  • 36eef3c Merge pull request #2801 from BridgeAR/fix-global-deprecation
  • 5304f86 Fix deprecation warning about GLOBAL
  • d5fe0fd Merge pull request #2769 from theel0ja/patch-1
  • 5b8c0fd Fix mixed content warning
  • 0763ab3 Fixes #2764 — Underscore should not have any dependencies.
  • c0e8fef Merge pull request #2763 from gonzalez/karma-sauncelabs-fix
  • 2e57316 updating addEventListener to support older browsers
  • 1dfec11 Pulling index.html from the published version.
  • 5499308 Remove old unmonitored Freenode link.

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 Jan 6, 2020

After pinning to 1.9.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