技能 2026-09-04 07:17 UTC
notebooklm-mcpv3.2.0
版本【v3.2.0】由提交人 roomi-fields 提交,主要更新类型为:依赖版本升级与工程管线维护。提交说明:ci: publish to npm by OIDC trusted publishing, with no stored token。保持依赖组件处于最新健康状态,保障工程测试与交付自动化。
Commit提交信息原文
ci: publish to npm by OIDC trusted publishing, with no stored token The stored Automation token expired for the second time — created 2026-02-27, rotated 2026-05-27, dead again by 2026-09-03, on npm's silent ~90-day cycle. Both times the failure surfaced as `404 Not Found - PUT` on a package that plainly exists, which is what npm returns for an unauthenticated write so as not to reveal whether the name is taken. Both times it cost an hour before anyone realised it was an auth error wearing a 404. The runner now proves its own identity to the registry with a short-lived OIDC token, so there is nothing to store, leak, rotate or rediscover. The trusted publisher is configured npm-side against this repository and this workflow file; `id-token: write` was already granted here for the MCP Registry job, which has authenticated this way since 3.0.x. Node 20 → 24, because the OIDC handshake needs npm >= 11.5.1 and Node 20 ships npm 10 — which would quietly fall back to hunting for the token that is now deliberately absent. `NPM_TOKEN` is no longer read by anything and can be revoked at npm and deleted from the repository secrets. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>