deps(dev): bump electron from 30.0.9 to 30.1.0

[dependabot]

Bumps electron from 30.0.9 to 30.1.0.

Release notes

Sourced from electron's releases.

electron v30.1.0

Release Notes for v30.1.0

Fixes

• BrowserWindow.show() now correctly restores focus to inactive apps on macOS. #42306 (Also in 31)
• Fixed BrowserWindow vibrancy on macOS. #42263
• Fixed an issue where BrowserView webContents were getting destroyed even when preventDefault was being set on the owning BrowserWindow's close event. #42371
• Fixed an issue where dialogs did not work if they were parented to a BaseWindow and not a BrowserWindow. #42327 (Also in 31)
• Fixed an issue where some calls to WebUSB methods could crash. #42364 (Also in 29, 31)

Other Changes

• Updated Chromium to 124.0.6367.243. #42328
• Updated Node.js to v20.14.0. #42294

Commits

• 4c96ced fix: WebUSB should not crash when using in-memory partitions (#42364)
• e645ea8 fix: vibrant view is inserted into Views API hierarchy (#42263)
• 484cf26 fix: don't destroy BrowserView webContents when owning BrowserWindow hasn't b...
• fb6b8e9 chore: bump chromium to 124.0.6367.243 (30-x-y) (#42328)
• 3be3381 chore: bump node to v20.14.0 (30-x-y) (#42294)
• 5523d91 fix: dialogs should work with BaseWindows internally (#42327)
• 6cb747e fix: restore original BrowserWindow.show() behavior (#42306)
• ebe3d4a build: update typescript-definitions to 8.15.6 (#42286)
• See full diff 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)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/electron@30.1.0	Transitive: environment, filesystem, network, shell	+32	5.04 MB

🚮 Removed packages: npm/electron@30.0.9

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Install scripts	npm/electron@30.0.9	Install script: postinstall Source: node install.js

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/electron@30.0.9