Skip to content

fix: use corepack to update npm for OIDC support - #34

Merged
maplezzk merged 2 commits into
mainfrom
fix/oidc-npm-version
Apr 28, 2026
Merged

maplezzk merged 2 commits into
mainfrom
fix/oidc-npm-version

Conversation

@maplezzk

Copy link
Copy Markdown
Owner

问题

今天 npm@latest 出了 bug(MODULE_NOT_FOUND: promise-retry),导致之前一直能用的 npm install -g npm@latest 步骤失败。PR #30 删除了这个步骤,但 Node 22 自带的 npm 10.x 对 OIDC 支持不完整——provenance 能签名成功,但 npm publish 的 PUT 请求认证会失败返回 404。

随后的 PR #33 误判为 registry-url 的问题将其移除,导致 OIDC 完全没触发(ENEEDAUTH)。

修复

  1. 恢复 registry-url — OIDC token 交换需要它来知道目标 registry
  2. 用 corepack 替代 npm install -g 升级 npm — 绕过 npm@latest 的 promise-retry bug
- name: Update npm for OIDC support
  run: |
    corepack enable npm
    corepack prepare npm@latest --activate
    npm --version

corepack 直接从 registry 下载 npm 包,不依赖本地 npm 是否损坏。

Claude Bot and others added 2 commits April 28, 2026 23:29
Restore registry-url (required for OIDC token exchange) and replace the
broken 'npm install -g npm@latest' with corepack to upgrade npm.

npm@latest has a MODULE_NOT_FOUND bug (missing promise-retry) as of
2026-04-28. corepack bypasses the corrupted npm binary to install a
clean version. npm 11+ is required for proper OIDC auto-detection in
GitHub Actions.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@maplezzk
maplezzk merged commit 493c811 into main Apr 28, 2026
1 check passed
@maplezzk
maplezzk deleted the fix/oidc-npm-version branch April 28, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant