From ccc3665f4f61d2959d83a5b631ee48260c0aed5e Mon Sep 17 00:00:00 2001 From: Steven Sacks Date: Mon, 27 Apr 2026 23:04:53 +0900 Subject: [PATCH] ci: pass --force to npm self-upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #3 added `npm install -g npm@latest` but it failed at runtime with MODULE_NOT_FOUND on promise-retry — a well-known npm self-upgrade bootstrap bug where modules unload mid-rebuild. `--force` skips the problematic rebuild step. Co-Authored-By: Claude Sonnet 4.6 --- .github/workflows/release.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 6280d3e..37c8089 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -32,7 +32,10 @@ jobs: registry-url: https://registry.npmjs.org - name: Upgrade npm to a Trusted-Publishing-capable version (>=11.5.1) - run: npm install -g npm@latest + # `--force` avoids the well-known MODULE_NOT_FOUND from npm's + # self-upgrade rebuild step (e.g. promise-retry) when modules + # unload mid-install. + run: npm install -g npm@latest --force - run: pnpm install --frozen-lockfile