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 url-loader is breaking the build 🚨 #22

Open
greenkeeper bot opened this issue Oct 10, 2018 · 1 comment
Open

An in-range update of url-loader is breaking the build 🚨 #22

greenkeeper bot opened this issue Oct 10, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 10, 2018

The devDependency url-loader was updated from 1.1.1 to 1.1.2.

🚨 View failing branch.

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

url-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.1.2

2018-10-10

Bug Fixes

  • fallback options behaviour (#145) (03e631f)
  • package: add support for webpack =< v3.0.0 (peerDependencies) (#150) (a6860fc)
  • package: relax node version range (engines) (#155) (d37b108)
  • utils/normalizeFallback: correctly pass all options to the default fallback (file-loader) (#139) (401be63)
Commits

The new version differs by 4 commits.

  • 0bbe0b8 chore(release): 1.1.2
  • d37b108 fix(package): relax node version range (engines) (#155)
  • fb465ad Fix doc formating (#153)
  • a6860fc fix(package): add support for webpack =< v3.0.0 (peerDependencies) (#150)

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
Author

greenkeeper bot commented Oct 10, 2018

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