An in-range update of aegir is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
The devDependency aegir was updated from 20.3.1 to 20.3.2.
π¨ View failing branch.
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
Release Notes for v20.3.2
Bug Fixes
- remove electron from the defaults target (9ff4633)
- remove manual push after rc publish (#432) (dfc5bb5), closes #426
Features
Commits
The new version differs by 5 commits.
b34dfdcchore: release version v20.3.22ddd594chore: update contributors9ff4633fix: remove electron from the defaults targetdfc5bb5fix: remove manual push after rc publish (#432)8b1cf8afeat: prefix rc with release (#431)
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.3.1 your tests are passing again. Downgrade this dependency π.
- The
devDependencyaegir was updated from20.3.2to20.4.0.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
devDependencyaegir was updated from20.4.0to20.4.1.
Your tests are still failing with this version. Compare changes
Commits
The new version differs by 6 commits.
5ddc875chore: release version v20.4.1b51dc04chore: update contributors5ed2fbefix: force --verbose for verbose mode (#447)06f0e03chore: release version v20.4.06d97934chore: update contributors39ed250feat: allow testing branches of third party repos (#438)
See the full diff