Update dependency electron to v43.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
electron	43.2.0 → 43.3.0

---

Release Notes

electron/electron (electron)

v43.3.0: electron v43.3.0

Compare Source

Release Notes for v43.3.0

Features

• Added available to process.getSystemMemoryInfo() on Linux, exposing proc/meminfo MemAvailable. #​52379 ^{(Also in 42, 44)}

Fixes

• Fixed BrowserWindow size corruption on Windows when created with explicit x/y on a secondary monitor whose DPI differs from the primary. #​52501 ^{(Also in 42, 44)}
• Fixed Dirent.parentPath being undefined for fs.readdir, fs.readdirSync, fs.glob, and fs.globSync with withFileTypes: true inside asar archives. #​52505 ^{(Also in 42, 44)}
• Fixed dialog.showOpenDialog/dialog.showSaveDialog opening at an unusable location on Linux when defaultPath is a bare filename without a directory. #​52401 ^{(Also in 44)}
• Fixed a UAF with protocol.registerStreamProtocol when an error is emitted during a read. #​52514 ^{(Also in 41, 42, 44)}
• Fixed a crash that could occur when closing DevTools while the host WebContents was being destroyed. #​52510 ^{(Also in 41, 42, 44)}
• Fixed a graphical glitch on Linux where thin borders appeared past the drop shadows on frameless windows when multiple windows were created. #​52607 ^{(Also in 44)}
• Fixed an issue where loading ICO files from ASAR archives on Windows left temporary icon files behind. #​52478 ^{(Also in 42, 44)}
• Fixed an issue where some values passed into requestSingleInstanceLock could result in a crash. #​52471 ^{(Also in 44)}

Other Changes

• Fixed bindings for MV3 service workers. #​52503
• Improved the error message when an asar integrity check fails to name the entry that failed. #​52622 ^{(Also in 42, 44)}
• Updated Chromium to 150.0.7871.212. #​52524
• Updated Node.js to v24.18.1. #​52552

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • "after 2am and before 8am on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eesast-web@2024.0.0
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   graphql@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^15.0.0 || ^16.0.0" from @apollo/client@3.14.1
npm error node_modules/@apollo/client
npm error   @apollo/client@"3.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-06T20_25_12_242Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-06T20_25_12_242Z-debug-0.log