Open greenkeeper[bot] opened 5 years ago
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.
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
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 π
The dependency npm was updated from
6.9.0
to6.9.1
.π¨ View failing branch.
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](https://travis-ci.org/frankthelen/npmaudit2slack/builds/551412517?utm_source=github_status&utm_medium=notification)).Release Notes for v6.9.1
BUGFIXES
6b1a9da0e
#165 UpdateknownBroken
version. (@ljharb)d07547154
npm.community#5929 Fixoutdated
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](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: