Files
Nate Sesti 300b2992c6 Fix npm OIDC: Node 24 for publish, unset bogus token (#10964)
* Remove beta release workflow and simplify stable release

Beta release is no longer used. Remove the workflow and simplify the
stable release to only support direct releases with a required version
input.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Fix npm OIDC: restore registry-url, clear NODE_AUTH_TOKEN, use Node 22

Previous fix removed registry-url entirely, causing ENEEDAUTH (no auth
at all). The correct approach: keep registry-url so npm knows the
endpoint, but clear NODE_AUTH_TOKEN at publish time so npm falls back
to OIDC. Also bump to Node 22 which ships with npm OIDC support.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Fix npm OIDC: use Node 24 for publish, unset bogus NODE_AUTH_TOKEN

Root cause: setup-packages resets Node to v20 (from .nvmrc), wiping
the npm upgrade. Node 20 ships with npm 10.x which has no OIDC
support. Fix: switch to Node 24 (ships with npm 11.5.1+) right before
publish, and unset the bogus NODE_AUTH_TOKEN that setup-node creates.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 16:46:46 -08:00
..
2025-03-16 12:03:17 -07:00