Closed greenkeeper[bot] closed 1 year ago
After pinning to 1.8.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
net::ERR_INSECURE_RESPONSE
on https error. #12117Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
devDependency
electron was updated from 4.0.5
to 4.0.6
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
electron was updated from 4.0.6
to 4.0.7
.Your tests are passing again with this update. Explicitly upgrade to this version π
defaultId
not taking affect when set to 0
and no "cancel" button was present on macOS. #17151process.versions.chrome
reporting the wrong patch version. #17218webContents.print()
not working correctly. #17116ShowOpenDialog
and ShowSaveDialog
. #17176devDependency
electron was updated from 4.0.7
to 4.0.8
.Your tests are passing again with this update. Explicitly upgrade to this version π
Release Notes TBD.
devDependency
electron was updated from 4.0.8
to 4.1.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
Please note that there are no new features in this release. Electron 4.1.0 was released to work around issues users were experiencing with node-pre-gyp
based native modules and our ABI number in Electron >= 4.0.4.
segments
array and remove label
or image
dynamically. #17335devDependency
electron was updated from 4.1.0
to 4.1.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
electron was updated from 4.1.1
to 4.1.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
nativeImage.createFromBuffer
/ nativeImage.addRepresentation
. Data URLs only parsed according to the MIME type as PNG or JPEG. #17567ICU_ENABLE_TENTATIVE_ERA
to true to enable the placeholder era. #17518win.isVisible()
on macOS. #17492.framework
files on macOS now have the correct permissions. This fixes an issue where a crash occurred if a user attempted to launch an Electron app that another user downloaded on macOS. #17582devDependency
electron was updated from 4.1.2
to 4.1.3
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
electron was updated from 4.1.3
to 4.1.4
.Your tests are passing again with this update. Explicitly upgrade to this version π
process.getProcessMemoryInfo
not being exposed to sandbox renderers. #17669
Version 1.7.6 of electron just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As electron is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/bitovi/launchpad/builds/272636787?utm_source=github_status&utm_medium=notification)Release Notes
electron v1.7.6Bug Fixes
WebContents
#9819Linux
macOS
code
anddomain
as properties to error events emitted byautoUpdater
module #10125TouchBarScrubber.continuous
was getting ignored #10133Windows
accept
file types #10015API Changes
BrowserView.fromId()
which returned theBrowserView
with the givenid
#10039BrowserWindow.addExtension
,BrowserWindow.removeExtension
,BrowserWindow.getExtensions
to add/remove/get Chrome extensions in an Electron app #9918macOS
treatPackageAsDirectory
flag todialog.showOpenDialog
, in order to treat packages, such as .app folders, as a directory instead of a file #9834Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: