Upgrade electron to version 24.1.3 #195
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 → ^24.1.3) · Repo
Release Notes
24.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
docs: fix start highlight tutorial-2-first-app.md (#38113)fix: webContents return type incorrect (#38111)chore: always lint JS in docs/fiddles (#38108)chore: cherry-pick 1 changes from Release-2-M112 (#38082)fix: crash in utilityProcess when generating code from strings (#38041)chore: bump chromium to 112.0.5615.165 (24-x-y) (#38047)fix: defaults broken in shell.openExternal() options (#38072)chore: bump chromium to 112.0.5615.138 (24-x-y) (#38031)build: fix building with no PDF support (#38007)chore: initial linting fixes for JS in docs/fiddles (#37838)docs: add note to `win.setFullScreen(flag)` (#37996)chore: replace uses of `ComPtr::GetAddressOf()` with `ComPtr::operator&` (#37992)docs: update github.com links (#37989)chore: bump chromium to 112.0.5615.121 (24-x-y) (#37985)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