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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of @types/jest is breaking the build 馃毃 #977

Closed
greenkeeper bot opened this issue Aug 5, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

commented Aug 5, 2019

The devDependency @types/jest was updated from 24.0.16 to 24.0.17.

馃毃 View failing branch.

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

@types/jest 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
  • now: Deployment has failed (error: #t7WWXGx) (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • codecov/project: No report found to compare against (Details).
  • codecov/patch: Coverage not affected. (Details).

FAQ and help

There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 馃尨

@greenkeeper greenkeeper bot added the greenkeeper label Aug 5, 2019

@issue-label-bot issue-label-bot bot added the bug 馃悶 label Aug 5, 2019

@issue-label-bot

This comment has been minimized.

Copy link

commented Aug 5, 2019

Issue-Label Bot is automatically applying the label bug 馃悶 to this issue, with a confidence of 0.82. Please mark this comment with 馃憤 or 馃憥 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

commented Aug 5, 2019

After pinning to 24.0.16 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@gr2m gr2m closed this Aug 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can鈥檛 perform that action at this time.