chore(deps-dev): bump @electron/asar from 3.4.1 to 4.3.0

[dependabot]

Bumps @electron/asar from 3.4.1 to 4.3.0.

Release notes

Sourced from @​electron/asar's releases.

v4.3.0

4.3.0 (2026-08-18)

Features

• store duplicated file contents only once when packing (#465) (01bc908)

v4.2.1

4.2.1 (2026-07-21)

Bug Fixes

• add circular symlink detection and depth limit protection (#423) (fd0fcd8)
• add DoS validation for asar archive headers and file entries (#419) (51cd188)
• add header validation for ASAR archives (#421) (00e5293)
• add offset validation to readFileSync to prevent out-of-bounds reads (#420) (97c09cc)
• add path validation to prevent directory traversal attacks (#418) (de0689b)
• compute integrity over transformed bytes when a transform is applied (#450) (8c9be01), closes #277
• constrain extractFile reads to the unpacked directory (#451) (1f4b01d)
• improve symlink validation to prevent directory traversal attacks (#422) (c43f92b)
• replace commander with native Node.js parseArgs (#416) (42b25d0)
• resolve absolute symlink targets correctly when packing (#452) (0087cfa), closes #366

v4.2.0

4.2.0 (2026-03-31)

Features

• Revert "feat: add integrity digest management commands and functional… (#424) (49681b1), closes #380

v4.1.2

4.1.2 (2026-03-28)

Performance Improvements

• 5-7x faster packing, 15-20% faster extraction (#414) (79686b6), closes #417

v4.1.1

4.1.1 (2026-03-24)

Bug Fixes

• pickle resize overflow, stream flush race, integrity block boundary (#413) (f1f0a8f)

v4.1.0

... (truncated)

Commits

• 01bc908 feat: store duplicated file contents only once when packing (#465)
• 2bf3408 build(deps): bump postcss from 8.5.20 to 8.5.24 (#463)
• ab7bc41 build(deps): bump undici from 7.28.0 to 7.29.0 (#462)
• d934f9a build(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#459)
• 1ce80a7 build(deps): bump actions/checkout from 7.0.0 to 7.0.1 (#460)
• 9428c25 build(deps): bump brace-expansion from 5.0.7 to 5.0.8 (#461)
• c4354ae ci: stop setting the Opened project field (#456)
• 8e12da2 build(deps): bump postcss from 8.5.15 to 8.5.20 (#458)
• 4d5d687 build(deps): bump linkify-it from 5.0.1 to 5.0.2 (#457)
• 0959a13 build(deps): bump brace-expansion from 5.0.6 to 5.0.7 (#455)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​electron/asar since your current version.

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

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 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)

[Astro-Han]

I reviewed this PR at exact head 775ab7a7b22345defcbcc0d072e4ba2ba9a92f38 (base 6762085e, 2 files +288−73, 1 commit).

Spec: GO — no P0–P3

• The change is strictly limited to package.json and the mechanically generated package-lock.json; the direct dev dependency is precisely bumped from 3.4.1 to 4.3.0, and the nested 3.4.1 is retained only for Electron tooling that still declares a v3 range.
• The official v4 breaking requirements are Node >=22.12.0, ESM-only, removal of the default export, and CLI moved to bin/asar.mjs. Maka declares Node >=22.19.0, uses only the named API, and does not depend on the old CLI path.
• Under the exact minimum Node 22.19.0, the existing createRequire(...).require('@electron/asar') loads v4.3.0 correctly; the real archive focused suite is 18/18 PASS (createPackage / getRawHeader / extractFile compatible). The same suite is 18/18 on local Node 26.
• Windows lookup separator adaptation remains compatible with v4.3.0; the hosted package and owner-platform lanes already cover the current artifact.

The lockfile growth is the expected npm representation after the v4 root can no longer be deduplicated with nested consumers that still need v3.

Standards: 2×P3 — non-blocking but needs housekeeping

1. P3 — PR template was replaced. Per CONTRIBUTING.md:81, the .github/pull_request_template.md should be filled; the stock Dependabot body lacks Verification, AI use, Checklist, and behavior-change declaration. This should be completed, or an automation exception should be documented in governance.
2. P3 — branch name does not match <type>/<description>. Per CONTRIBUTING.md:83 and Dependabot's dependabot/npm_and_yarn/electron/asar-4.3.0 pattern, the generated branch conflicts with the rule. Since .github/dependabot.yml explicitly enables this automation, the practical fix is to record a bot exception rather than forcing a rename of a generated branch.

No Fowler judgment smell; the package/lock delta is mechanical and entropy-neutral. Title, bot identification, Signed-off-by, Node floor, and API compatibility otherwise pass.

Other checks: git diff --check passes; test, audit, package, windows_recovery, and owner macOS/Windows checks are all terminal SUCCESS for this exact head; OPEN / MERGEABLE / BLOCKED / REVIEW_REQUIRED, no reviews/comments, head did not drift.

What I did not check: full local suite beyond the focused 18/18 archive checks.

Gate: exact head has no P0–P2 and all required checks are green. The two P3 template/branch findings are non-blocking housekeeping; the PR can be approved and merged once the automation exception is acknowledged, or the template is completed.

---

Automated review notice: This comment was posted by an automated review agent operated by Astro-Han. It is not an independent human review and does not replace one.

[Astro-Han]

Bumps the @electron/asar devDependency from 3.4.1 to 4.3.0, a major bump, touching only package.json and package-lock.json.

What I checked, since a major bump is not automatically safe:

• Our entire API surface is three calls: createPackage in scripts/verify-packaged-app.test.mjs:160, and getRawHeader / extractFile in scripts/verify-packaged-app.mjs:813,829,948,951,973. All three still exist in 4.x. We never touch the CLI, so 4.x replacing commander reaches nothing of ours.
• @electron/asar@4.3.0 declares engines.node: >=22.12.0, which our >=22.19.0 already satisfies.
• The package check is green. That job actually packages and verifies a real archive, so the three calls above ran against 4.3.0 rather than merely typechecking. That, and not the changelog, is what makes this safe to take.
• 4.x is mostly hardening of archive parsing (header validation, offset bounds, symlink traversal, depth limits). We only read archives we just built, so this is not a live exposure being closed, but it is the direction we want the dependency to move.

Approving.

AI use: Claude Code (Opus) enumerated our call sites, checked the declared engine range against ours, and confirmed the package job exercises the archive path. The reviewer of record reviewed and accepted this.

简体中文

将 devDependency @electron/asar 从 3.4.1 升到 4.3.0，跨大版本，只改 package.json 和 package-lock.json。

跨大版本不能默认安全，所以核对了：

• 我们用到的 API 只有三个：verify-packaged-app.test.mjs:160 的 createPackage，以及 verify-packaged-app.mjs:813,829,948,951,973 的 getRawHeader / extractFile。三者在 4.x 中均在。我们不用它的 CLI，因此 4.x 换掉 commander 影响不到我们。
• @electron/asar@4.3.0 声明 engines.node: >=22.12.0，我们的 >=22.19.0 满足。
• package 检查已绿。该 job 会真正打包并校验归档，所以上面三个调用是在 4.3.0 上真跑过，而不只是过了类型。让这次升级可接受的是这一点，不是 changelog。
• 4.x 主要是归档解析加固（头部校验、偏移越界、符号链接穿越、深度限制）。我们只读自己刚构建的归档，所以并非在关闭一个现存暴露面，但这是我们希望该依赖走的方向。

Approve。