An in-range update of electron is breaking the build π¨
Closed this issue Β· 2 comments
The devDependency electron was updated from 4.1.2
to 4.1.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
electron 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 electron v4.1.3
Release Notes for v4.1.3
Fixes
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 4.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
electron was updated from4.1.3
to4.1.4
.
Your tests are passing again with this update. Explicitly upgrade to this version π
Release Notes for electron v4.1.4
Release Notes for v4.1.4
Fixes
- Backported fix for crashes in RenderFrameImpl::OnSelectPopupMenuItem(s). #17659
- Backported fix for https://bugs.chromium.org/p/chromium/issues/detail?id=888678. #17632
- Fixed
process.getProcessMemoryInfo
not being exposed to sandbox renderers. #17669 - Fixed re-entracy problem with InvalidateFrameSinkId(). #17658
- Fixed the --explicitly-allowed-ports switch. #17642
Documentation
- Documentation changes: #17662