Bump electron from 31.0.0 to 33.0.1

[dependabot]

Bumps electron from 31.0.0 to 33.0.1.

Release notes

Sourced from electron's releases.

electron v33.0.1

Release Notes for v33.0.1

Other Changes

• Updated Chromium to 130.0.6723.59. #44271

electron v33.0.0

Release Notes for 33.0.0

Stack Upgrades

• Chromium 130.0.6723.44
  • New in 130
  • New in 129
• Node 20.18.0
  • Node 20.18.0 blog post
  • Node 20.17.0 blog post
• V8 13.0

Breaking Changes

• Deprecated usage of textured BrowserWindow type option on macOS. #43133
• Custom protocol URLs that use Windows file paths will no longer work correctly with the deprecated protocol.registerFileProtocol and the baseURLForDataURL property on BrowserWindow.loadURL, WebContents.loadURL, and <webview>.loadURL. #43977

Features

Additions

• Added a handler, app.setClientCertRequestPasswordHandler(handler), to help unlock cryptographic devices when a PIN is needed. #41205
• Added error event in utility process to support diagnostic reports on V8 fatal errors. #43997
• Added View.setBorderRadius(radius) for customizing the border radius of views—with compatibility for WebContentsView. #42320
• Added Linux support for the Windows Control Overlay API. #41769 (Also in 30, 31, 32)
• Added support for the macOS system picker in desktopCapturer and setDisplayMediaRequestHandler. #43680 (Also in 32)
• Added DownloadItem.getCurrentBytesPerSecond(), DownloadItem.getPercentComplete(), DownloadItem.getEndTime(). #42805 (Also in 30, 31, 32)
• Added a new property prefersReducedTransparency to nativeTheme, which indicates whether the user has chosen to reduce OS-level transparency via system accessibility settings. #42862 (Also in 30, 31, 32)
• Added support for responding to auth requests initiated from utility process via app#login event. #42631 (Also in 32)

Improvements

• Extended navigationHistory API with 2 new functions for better history management. #42014
• Ensured that the sender-id hint is set when creating desktop notifications on DBus. #43949 (Also in 31, 32)
• Aligned failure pathway in File System Access API with upstream when attempting to open a file or directory in a blocked path. #42561 (Also in 30, 31, 32)
• Enabled zstd compression in net http requests. #43150 (Also in 31, 32)
• Expose systemPreferences to utilityProcess. #42203 (Also in 30, 31, 32)

Fixes

• Fixed a build failure when the enable_plugins build flag is false. #44025
• Fixed mouse cursor turning into loading spinner when starting utility process on Windows. #43731

... (truncated)

Changelog

Sourced from electron's changelog.

Breaking Changes

Breaking changes will be documented here, and deprecation warnings added to JS code where possible, at least one major version before the change is made.

Types of Breaking Changes

This document uses the following convention to categorize breaking changes:

• API Changed: An API was changed in such a way that code that has not been updated is guaranteed to throw an exception.
• Behavior Changed: The behavior of Electron has changed, but not in such a way that an exception will necessarily be thrown.
• Default Changed: Code depending on the old default may break, not necessarily throwing an exception. The old behavior can be restored by explicitly specifying the value.
• Deprecated: An API was marked as deprecated. The API will continue to function, but will emit a deprecation warning, and will be removed in a future release.
• Removed: An API or feature was removed, and is no longer supported by Electron.

Planned Breaking API Changes (34.0)

Deprecated: level, message, line, and sourceId arguments in console-message event on WebContents

The console-message event on WebContents has been updated to provide details on the Event argument.

// Deprecated
webContents.on('console-message', (event, level, message, line, sourceId) => {})
// Replace with:
webContents.on('console-message', ({ level, message, lineNumber, sourceId, frame }) => {})

Additionally, level is now a string with possible values of info, warning, error, and debug.

Planned Breaking API Changes (33.0)

Behavior Changed: frame properties may retrieve detached WebFrameMain instances or none at all

APIs which provide access to a WebFrameMain instance may return an instance with frame.detached set to true, or possibly return null.

When a frame performs a cross-origin navigation, it enters into a detached state in which it's no longer attached to the page. In this state, it may be running unload handlers prior to being deleted. In the event of an IPC sent during this state, frame.detached will be set to true with the frame being destroyed shortly thereafter.

When receiving an event, it's important to access WebFrameMain properties immediately upon being received. Otherwise, it's not guaranteed to point to the same webpage as when received. To avoid misaligned expectations, Electron will return null in the case of late access where the webpage has changed.

... (truncated)

Commits

• 11c2b61 chore: bump chromium to 130.0.6723.59 (33-x-y) (#44271)
• 6b458c7 fix: -Wunsafe-buffer-usage warnings in TaskbarHost::SetThumbarButtons() (#44260)
• 77324ff build: update devcontainer sha (#44245)
• 63d1d9c fix: SCContentSharingPicker crash in iframes (#44228)
• dd5bce1 docs: update timelines for E34 (#44225)
• 258a4a7 fix: -Wunsafe-buffer-usage warning in ChunkedDataPipeReadableStream (#44223)
• f269ca1 test: fix visibility-state-spec.ts flaky test (#44199)
• 7887395 fix: -Wunsafe-buffer-usage warnings when read()ing and write()ing integers (#...
• 9011532 fix: clang variable configuration in generated node headers (#44200)
• afce3ce docs: clarify interplay between utility process events (#44203)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #68.