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 @types/jasmine is breaking the build 🚨 #136

Open
greenkeeper bot opened this issue Mar 19, 2019 · 5 comments
Open

An in-range update of @types/jasmine is breaking the build 🚨 #136

greenkeeper bot opened this issue Mar 19, 2019 · 5 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 19, 2019

The devDependency @types/jasmine was updated from 3.3.11 to 3.3.12.

🚨 View failing branch.

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

@types/jasmine 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).

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 Mar 19, 2019

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 28, 2019

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 19, 2019

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 22, 2019

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 26, 2019

Your tests are still failing with this version. Compare changes

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