An in-range update of @types/node is breaking the build 🚨

Question

An in-range update of @types/node is breaking the build 🚨

Opened this issue 8 years ago · 21 comments

Version 7.0.9 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.8
Type	devDependency

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

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Answer 1 · 2017-03-22T23:58:24.000Z

Version 7.0.10 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 2 · 2017-03-25T01:39:36.000Z

Version 7.0.11 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 3 · 2017-03-27T23:22:15.000Z

Version 7.0.12 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 4 · 2017-04-18T15:39:47.000Z

Version 7.0.13 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 5 · 2017-04-26T18:02:30.000Z

Version 7.0.14 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 6 · 2017-05-01T21:16:53.000Z

Version 7.0.15 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 7 · 2017-05-03T20:55:00.000Z

Version 7.0.16 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 8 · 2017-05-05T01:29:13.000Z

Version 7.0.17 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 9 · 2017-05-05T01:36:13.000Z

Version 7.0.18 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 10 · 2017-05-20T00:52:41.000Z

Version 7.0.19 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 11 · 2017-05-20T00:55:16.000Z

Version 7.0.20 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 12 · 2017-05-20T01:00:36.000Z

Version 7.0.21 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 13 · 2017-05-23T00:40:29.000Z

Version 7.0.22 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 14 · 2017-06-02T06:52:00.000Z

Version 7.0.23 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 15 · 2017-06-02T14:15:46.000Z

Version 7.0.24 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 16 · 2017-06-02T17:13:09.000Z

Version 7.0.25 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 17 · 2017-06-02T17:25:38.000Z

Version 7.0.26 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 18 · 2017-06-02T17:57:19.000Z

Version 7.0.27 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 19 · 2017-06-06T14:54:14.000Z

Version 7.0.28 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 20 · 2017-06-07T17:10:19.000Z

Version 7.0.29 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Answer 21 · 2017-06-19T16:09:05.000Z

Version 7.0.32 just got published.

Your tests are still failing with this version. Compare the changes 🚨