An in-range update of @oclif/command is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
Version 1.4.31 of @oclif/command was just published.
Branch | Build failing π¨ |
---|---|
Dependency |
@oclif/command
|
Current Version | 1.4.30 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@oclif/command 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
- β ci/circleci: test Your tests failed on CircleCI Details
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 π΄
Version 1.4.32 just got published.
Your tests for group default are passing again with this version. Explicitly upgrade default to this version π
After pinning to 1.4.30 your tests are passing again. Downgrade this dependency π.
Version 1.4.33 just got published.
Your tests for group default are passing again with this version. Explicitly upgrade default to this version π
Commits
The new version differs by 7 commits.
cf169e6
chore(release): 1.4.33 [skip ci]
b6bd279
fix: bump @oclif/parser
cee5715
[FEAT] bump @oclif/parse version to latest
c255811
Revert "[FIX] bump parse version dependency"
1c9a510
[FIX] bump parse version dependency
56fc124
chore(release): 1.4.32 [skip ci]
4bf98c4
fix: imports
See the full diff