Open greenkeeper[bot] opened 4 years ago
After pinning to 1.12.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
resolve was updated from 1.12.1
to 1.12.2
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.12.2
to 1.13.0
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.13.0
to 1.13.1
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.13.1
to 1.14.0
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.14.0
to 1.14.1
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.15.0
to 1.15.1
.Your tests are still failing with this version. Compare changes
The new version differs by 12 commits ahead by 12, behind by 1.
c1750d6
v1.15.1
5e1f5c8
[Dev Deps] update @ljharb/eslint-config
891bd89
[Fix] correct behavior when requiring .
with same name (#212)
16c1170
[Tests] allow node 5 on windows to fail due to npm registry bug
9529db4
v1.15.0
f0ad85f
[Dev Deps] update eslint
, @ljharb/eslint-config
, tape
7b80058
[Refactor] sync
: add function name
163f9da
[New] sync
'/async
: Implement packageIterator
(#205)
fca4013
[Refactor] remove useless exports
assignment
9fea81a
v1.14.2
b261110
[Fix] sync
/async
: Fixes isCore check (#206)
2f0e047
v1.14.1
See the full diff
dependency
resolve was updated from 1.15.1
to 1.16.0
.Your tests are still failing with this version. Compare changes
dependency
resolve was updated from 1.16.0
to 1.16.1
.Your tests are still failing with this version. Compare changes
The dependency resolve was updated from
1.12.0
to1.12.1
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
resolve 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/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/adamkeinan/metro-desktop/builds/29042210)).Commits
The new version differs by 7 commits.
ecd0672
v1.12.1
9f06a8f
fix: packageFilter passes expected arguments
ed46ce6
[Fix]
sync
:packageFilter
: whenpreserveSymlinks
isfalse
, realpath thepkgfile
optionda3c48f
[Tests] use shared travis-ci configs
de8aae6
[meta] add
funding
field9c18844
[Docs] fix CI status badge
8a8c218
[Dev Deps] update
eslint
,@ljharb/eslint-config
,safe-publish-latest
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: