An in-range update of lerna is breaking the build π¨
greenkeeper opened this issue Β· comments
The devDependency lerna was updated from 3.5.1
to 3.6.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
lerna is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 23 commits.
8cc3196
chore(release): publish v3.6.0
54008c6
feat(npm-dist-tag): Use fetch API instead of CLI to make changes
b387881
feat(listable): Add --toposort option
65a1d1b
feat(create): Migrate
npm info
subprocess to libnpm.manifest7411299
chore: bump eslint-plugin-jest, auto-fix warnings
e00dc0f
chore: bump prettier
7a7e135
chore: update lockfile with missing local dep
2639bba
test: Move shared command fixtures into root
4017f37
fix(pkg): Exclude mocks from package tarball
0d3a786
feat: Migrate existing usage to libnpm
732d850
chore(travis): Do not allow failures on Node 11
35fc3a7
chore(travis): Remove horrendously slow Windows executions
e2cb8f5
chore(ci): give up on azure pipelines again
0f97944
ci(azure): Add yarn, configure git user, and limit to node 10
e6748fb
chore(ci): Set up Azure Pipelines
There are 23 commits in total.
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 π΄
After pinning to 3.5.1 your tests are passing again. Downgrade this dependency π.
Fixed by 3.1.1 release