Upgrade electron to version 10.1.2 #60
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ electron (^8.2.5 → ^10.1.2) · Repo
Release Notes
10.1.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Bump v10.1.2fix: handle electron script errors better (#25331) (#25452)fix: Ensure electron delay loads the same modules as chromium (#25435)fix: bind fake mojo service for badging (#25369)chore: sync 10-x-y release notes script to master (#25304)feat(extensions): add support for some chrome.management APIs (#25098) (#25345)fix: avoid creating client_id file for empty DIR_CRASH_DUMPS (#25309)fix: only focus a webContents if the window was not initially hidden (#25323) (#25330)fix: multiple dock icons when calling dock.show/hide (#25299)chore: bump chromium to 85.0.4183.98 (10-x-y) (#25275)chore: bump chromium in DEPS to 85.0.4183.94 (#25255)ci: cleanup up test app directories (#25256)chore: force source code and markdown files to use LF line ending (#25175)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands