build(ci): upgrade Electron to v29.3.0, ci Node to v20.9.0 - #3132
Closed
twhy wants to merge 1 commit into
Closed
Conversation
Contributor
|
The Electron 30 is now stable and could be a great option for an upgrade |
Contributor
Author
|
Yes. Electron 30 was released two days ago. |
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Electron 29: Chromium 122.0.6261.39, V8 12.2, and Node.js 20.9.0.
Update CI Node to v20.9.0 to match with Electron v29's Node version.
We are not using features mentioned in Breaking Changes.
https://www.electronjs.org/blog/electron-29-0#breaking-changes
This upgrade fixes the
Intl.NumberFormat.prototype.format()issue metioned in #3219