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 vue-lazyload is breaking the build 🚨 #1221

Open
greenkeeper bot opened this issue Aug 9, 2019 · 2 comments
Open

An in-range update of vue-lazyload is breaking the build 🚨 #1221

greenkeeper bot opened this issue Aug 9, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Aug 9, 2019

The dependency vue-lazyload was updated from 1.3.1 to 1.3.2.

🚨 View failing branch.

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

vue-lazyload 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
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: unit_test: Your tests failed on CircleCI (Details).

Commits

The new version differs by 5 commits.

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

After pinning to 1.3.1 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 18, 2019

  • The dependency vue-lazyload was updated from 1.3.2 to 1.3.3.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 3 commits.

  • cd8df3d fix: #348
  • 35bb89c Merge pull request #397 from JialingC/master
  • f270672 Fix: 348 prevent to get null 404 (Not Found)

See the full diff

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