An in-range update of aegir is breaking the build 🚨
greenkeeper opened this issue · 3 comments
The devDependency aegir was updated from 20.1.0 to 20.2.0.
This version is covered by your current version range and after updating it in your project the build failed.
aegir 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
The buildRelease Notes for v20.2.0
Bug Fixes
- fix linter (903bd03)
Features
BREAKING CHANGES
- linter upgrade you may need to fix linting problems
Commits
The new version differs by 6 commits.
8500e2fchore: release version v20.2.0fa4db4achore: update contributors903bd03fix: fix linter36de3fffeat: adds command to update release candidates (#421)8d186afdocs: update travis config24ba24bfeat: update deps (#423)
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 20.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependencyaegir was updated from20.2.0to20.3.0.
Your tests are still failing with this version. Compare changes
Release Notes for v20.3.0
Bug Fixes
Features
Commits
The new version differs by 6 commits.
3edb1d0chore: release version v20.3.0f4adbd1chore: update contributors0444fcfMerge branch 'master' of github.com:ipfs/aegir92236bafeat: add test-external command (#425)d82815afix: push to the current branch (#426)61cc413feat: add AEGIR_RUNNER env var and support timeout in the browser and electron test runners.
See the full diff
- The
devDependencyaegir was updated from20.3.0to20.3.1.
Your tests are still failing with this version. Compare changes