chore(deps-dev): bump electron from 42.3.3 to 43.0.0 in the root-npm-dependencies group across 1 directory

[dependabot]

Bumps the root-npm-dependencies group with 1 update in the / directory: electron.

Updates electron from 42.3.3 to 43.0.0

Release notes

Sourced from electron's releases.

electron v43.0.0

Release Notes for v43.0.0

Stack Upgrades

• Chromium 150.0.7871.46
  • New in 150
  • New in 149
• Node v24.147.0
  • Node 24.17.0 blog post
• V8 15.0

Breaking Changes

• File downloads will open by default in the user's Downloads folder (or Home directory if Downloads doesn't exist). #49868
• Fix: If a nativeImage was passed an image with a color profile, its pixel values will now be normalized to SRGB. This ensures that two visually identical images after color space application will receive similar pixel values when converted to a nativeImage. #51565
• On Linux, frameless windows now have rounded corners by default, just like on macOS and Windows. Rounded corners can be disabled on all platforms by setting roundedCorners: false on the window. #52111
• Removed showHiddenFiles support from the dialog API on Linux. #51880

Features

Additions

• Added Clone method to WebContents. #49959
• Added JS stack trace to crash reports on renderer OOM. #50043 (Also in 42)
• Added Linux support for app.getApplicationInfoForProtocol(). #51297 (Also in 42)
• Added Notification.remove(), removeAll(), and removeGroup() static methods for macOS. #51690 (Also in 42)
• Added Notification.getHistory() for macOS, allowing developers to restore all delivered notifications still present in Notification Center. #50325 (Also in 42)
• Added accessibilityLabel property to MenuItem constructor options and properties for defining screen-reader-friendly labels. #50240
• Added allowExtensions privilege to protocol.registerSchemesAsPrivileged() to enable Chrome extensions on custom protocols. #49951 (Also in 40, 41, 42)
• Added app.configureWebAuthn() to enable the Touch ID platform authenticator for WebAuthn on macOS, and a select-webauthn-account session event for choosing between multiple discoverable credentials. #51255 (Also in 41, 42)
• Added globalShortcut.setSuspended() and globalShortcut.isSuspended() methods to temporarily suspend and resume global shortcut handling. #50425 (Also in 42)
• Added id and groupId options to the Notification constructor on macOS. id allows custom identifiers for notifications, and groupId visually groups notifications together in Notification Center. #50097 (Also in 42)
• Added nv12 OSR pixel format support for professional use. #49799
• Added view.setBackgroundBlur. #51076
• Added webContents.copyVideoFrameAt(x, y) and webContents.saveVideoFrameAs(x, y) methods. #48149
• Added id, groupId, and groupTitle support for Windows notifications. #50328 (Also in 42)
• Added nativeTheme.shouldDifferentiateWithoutColor on macOS. #49912 (Also in 41, 42)
• Added session support to net module requests from utility process. #51279 (Also in 42)
• Added support for heap profiling via contentTracing.enableHeapProfiling(). #50826 (Also in 41, 42)
• Added support for importing shared textures using the nv16 pixel format. #50728 (Also in 42)
• Added support for the urgency option in Notifications on Windows. #50225 (Also in 41, 42)
• Added support for using a proxy during yarn install. #50322 (Also in 39, 40, 41, 42)
• Allowed the --experimental-inspector-network-resource Node.js flag to be passed through Electron. #49689 (Also in 41, 42)
• Enabled ThinLTO on macOS builds. #51819 (Also in 42)
• Enabled profile-guided optimization for V8 builtins in release builds, improving JavaScript builtin performance (Array, String, RegExp, etc.). #50416 (Also in 40, 41, 42)
• Feat: SF Symbol customisation. #48911
• Fixed contentTracing module to capture Node.js trace categories. #50591

Improvements

• Improved app startup performance — the main process now boots from an embedded Node.js startup snapshot, framework bundles and preload scripts are cached as compiled V8 bytecode, and sandboxed renderer startup data is pushed ahead of navigation instead of fetched via blocking IPC. Preload stack traces now show the correct file path and line number. #51792 (Also in 42)

... (truncated)

Commits

• 5147ac2 test: fix lost-event race in custom-protocol-panel devtools fixture (#52194)
• 765def3 ci: improve lint job code reuse (#52180)
• 07f9757 fix: remove 1px frame background color from the top of frameless windows on L...
• 2e29d7f build: register Electron.app with LaunchServices before macOS tests (#52186)
• 3a77e4a fix: inherit iframe sandbox flags in windows opened on the OpenURL navigation...
• 3846728 chore: bump chromium to 150.0.7871.46 (43-x-y) (#52123)
• c0d5334 ci: calculate rerun apply patches date from first run attempt (#52075)
• 4a2ff4b build: only run gn-typescript-definitions for default toolchain (#52165)
• c3d3305 chore: cherry-pick 1 changes from chromium (#52168)
• dad4f73 fix: use the registering session for ProtocolResponse.url requests (#52131)
• Additional commits viewable in compare view

[itomek]

Verified locally on macOS arm64: with all four electron declarations at ^43.0.0, the packaged example app launches and renders on Electron 43.0.0 and the electron test suites pass. Pushed b5e43e7 to regenerate the two per-app lockfiles (example, jira) this group bump left at 42.3.3 — that mismatch is what was failing the build-apps / Test Electron Runtime jobs (npm ci: "lock file's electron@42.3.3 does not satisfy electron@43.0.0").

This PR now carries the complete, self-consistent upgrade; #1802 and #1804 are superseded by it and closed.

🔍 Verification details

• npx electron --version → v43.0.0
• tests/electron jest suites: 626/627 pass — the one failure is the pre-existing title assertion, identical on main since 2026-06-22 (run 27963725792); fix in fix(tests): match chat-app title assertion to renamed Agent UI title #1927
• Version-consistency suites (test_electron_functional.js, test_electron_framework_integration.js): pass once all four declarations agree at ^43 — which is why neither chore(deps-dev): bump electron from 42.3.3 to 43.0.0 in /src/gaia/apps/example/webui in the example-app-dependencies group across 1 directory #1802 nor chore(deps-dev): bump electron from 42.3.3 to 43.0.0 in /src/gaia/apps/jira/webui in the jira-app-dependencies group across 1 directory #1804 was independently mergeable
• Example + Jira apps packaged with electron-forge; example app launched with --remote-debugging-port, CDP /json/version User-Agent confirms Electron/43.0.0 (screenshot above)
• Agent UI Vitest suite: 109/109 pass locally; the CI red on that check is an order-dependent flake in SettingsPage.test.tsx (same code passes on chore(deps-dev): bump electron from 42.3.3 to 43.0.0 in /src/gaia/apps/jira/webui in the jira-app-dependencies group across 1 directory #1804's run)
• Expected remaining CI reds after rerun: "Test Electron Framework" / "Test Summary" (stale title fixture — fix(tests): match chat-app title assertion to renamed Agent UI title #1927) — pre-existing, not electron-related

Tested via: root npm ci + per-app npm ci --prefix ., full electron jest suites, and a packaged-app launch on this branch merged with main.

[itomek]

Upgrade verified locally end-to-end (packaged app on 43.0.0, full electron suites); lockfile sync pushed. Remaining reds are pre-existing main issues tracked in #1926/#1927.

[github-actions]

🟡 The main Agent UI (src/gaia/apps/webui/) was missed in this bump and still pins Electron at ^42.2.0 — even lower than the ^42.3.3 the other apps started from. Every other app and the root manifest are now on ^43.0.0, but the primary user-facing app will keep installing Electron 42.x from its own directory.

🔍 Technical details

src/gaia/apps/webui/package.json:73 still reads:

"electron": "^42.2.0",

Its package-lock.json was also not updated. This is the main Electron shell documented in CLAUDE.md ("Agent UI Frontend … React/TypeScript/Vite desktop app with Electron shell"), so it needs the same ^43.0.0 bump and a refreshed lockfile.