An in-range update of npm is breaking the build 🚨

Question

An in-range update of npm is breaking the build 🚨

greenkeeper opened this issue 5 years ago · comments

The dependency npm was updated from `6.9.0` to `6.9.1`.

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

npm 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

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

Release Notes for v6.9.1

BUGFIXES

6b1a9da0e #165 Update knownBroken version. (@ljharb)
d07547154 npm.community#5929 Fix outdated rendering for global dependencies. (@zkat)
e4a1f1745 npm.community#6259 Fix OTP for token create and remove. (@zkat)

DEPENDENCIES

a163a9c35 sha@3.0.0 (@aeschright)
47b08b3b9 query-string@6.4.0 (@aeschright)
d6a956cff readable-stream@3.2.0 (@aeschright)
10b8bed2b tacks@1.3.0 (@aeschright)
e7483704d tap@12.6.0 (@aeschright)
3242fe698 tar-stream@2.0.1 (@aeschright)

Commits

The new version differs by 12 commits.

43cb258 6.9.1
199c970 6.9.1-next.0
dcc759c doc: update changelog for npm@6.9.1
3242fe6 tar-stream@2.0.1
e748370 tap@12.6.0
10b8bed tacks@1.3.0
d6a956c readable-stream@3.2.0
47b08b3 query-string@6.4.0
a163a9c sha@3.0.0
e4a1f17 token: fix otp for create and remove (#175)
d075471 outdated: fix rendering for global dependencies (#173)
6b1a9da Update knownBroken version (#165)

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 · Answer 1 · Fri Jun 28 2019 00:57:53 GMT+0800 (China Standard Time)

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

greenkeeper · Answer 2 · Fri Jun 28 2019 04:14:18 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.9.1 to 6.9.2.

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

Commits

The new version differs by 2 commits.

31718e7 6.9.2
21eef31 doc: update changelog for npm@6.9.2

See the full diff

greenkeeper · Answer 3 · Thu Jul 04 2019 01:55:21 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.9.2 to 6.10.0.

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

greenkeeper · Answer 4 · Fri Jul 12 2019 01:46:56 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.10.0 to 6.10.1.

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

greenkeeper · Answer 5 · Wed Jul 24 2019 00:40:21 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.10.1 to 6.10.2.

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

greenkeeper · Answer 6 · Wed Aug 07 2019 00:59:03 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.10.2 to 6.10.3.

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

greenkeeper · Answer 7 · Wed Aug 21 2019 02:26:51 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.10.3 to 6.11.0.

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

greenkeeper · Answer 8 · Wed Aug 21 2019 08:25:59 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.11.0 to 6.11.1.

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

greenkeeper · Answer 9 · Fri Aug 23 2019 05:06:29 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.11.1 to 6.11.2.

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

greenkeeper · Answer 10 · Wed Sep 04 2019 06:39:10 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.11.2 to 6.11.3.

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

greenkeeper · Answer 11 · Tue Oct 08 2019 23:50:16 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.11.3 to 6.12.0.

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

greenkeeper · Answer 12 · Wed Oct 30 2019 01:14:53 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.12.0 to 6.12.1.

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

greenkeeper · Answer 13 · Wed Nov 06 2019 04:28:52 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.12.1 to 6.13.0.

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

greenkeeper · Answer 14 · Tue Nov 19 2019 18:10:15 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.0 to 6.13.1.

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

greenkeeper · Answer 15 · Wed Dec 04 2019 02:28:31 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.1 to 6.13.2.

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

greenkeeper · Answer 16 · Tue Dec 10 2019 09:40:55 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.2 to 6.13.3.

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

greenkeeper · Answer 17 · Thu Dec 12 2019 03:13:26 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.3 to 6.13.4.

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

greenkeeper · Answer 18 · Fri Jan 10 2020 05:45:17 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.4 to 6.13.5.

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

greenkeeper · Answer 19 · Fri Jan 10 2020 07:10:11 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.5 to 6.13.6.

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

greenkeeper · Answer 20 · Wed Jan 29 2020 03:21:07 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.6 to 6.13.7.

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

greenkeeper · Answer 21 · Fri Feb 28 2020 06:20:47 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.13.7 to 6.14.0.

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

greenkeeper · Answer 22 · Fri Feb 28 2020 16:53:11 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.14.0 to 6.14.1.

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

greenkeeper · Answer 23 · Wed Mar 04 2020 03:12:07 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.14.1 to 6.14.2.

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

greenkeeper · Answer 24 · Thu Mar 19 2020 23:28:50 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.14.2 to 6.14.3.

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

greenkeeper · Answer 25 · Thu Mar 26 2020 05:42:53 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.14.3 to 6.14.4.

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

greenkeeper · Answer 26 · Tue May 05 2020 00:54:22 GMT+0800 (China Standard Time)

The dependency npm was updated from 6.14.4 to 6.14.5.

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

An in-range update of npm is breaking the build 🚨

The dependency npm was updated from 6.9.0 to 6.9.1.

BUGFIXES

DEPENDENCIES

The dependency npm was updated from `6.9.0` to `6.9.1`.