fix(release): allow cli-entry.js in standalone dist allowlist (#5153)

The OOM-prevention work in #4914 added a dist/cli-entry.js bin wrapper
(re-spawns node --expose-gc cli.js) via prepare-package.js, but did not
register it in the standalone packager's strict dist allowlist. The
release job then fails with:

  Error: Unexpected dist asset: .../dist/cli-entry.js

Add cli-entry.js to DIST_ALLOWED_ENTRIES, same fix as #5049 did for
fzfWorker.js.
This commit is contained in:
易良 2026-06-15 18:11:03 +08:00 committed by GitHub
parent d219cfd2db
commit 511a22864b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -44,6 +44,9 @@ const DIST_REQUIRED_PATHS = [
];
const DIST_ALLOWED_ENTRIES = new Set([
'cli.js',
// bin wrapper emitted by prepare-package.js that re-spawns `node --expose-gc
// cli.js`; ships in dist/ as the package `bin` entry (#4914).
'cli-entry.js',
// fzf fuzzy-search worker; esbuild emits it as a standalone entry that must
// sit next to cli.js so `new URL('./fzfWorker.js', ...)` resolves at runtime.
'fzfWorker.js',