You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4841592
Browse filesBrowse the repository at this point in the historyBrowse files
Narrows runtime support to the current LTS instead of maintaining a matrix of
older ones: Node 22 is not EOL, this is a deliberate policy choice, not a
forced one. Bumps engines.node to >=24 and the CI matrix to a single Node 24
job (was 22+24, with three other jobs individually pinned to 22 as well).
actions/checkout and actions/setup-node go from @v4 to @v7 in both workflows.
@v4 pins its own internal JS runtime to Node 20, which GitHub is deprecating
(EOL April 2026, runners default to Node 24 from June 2026, full removal fall
2026) -- unrelated to this project's own node-version input, but every @v4
consumer gets the warning regardless. @v5+ moved the action's own runtime to
Node 24.
Also fixes a real defect the last release run just hit: "Tag and publish"
created and pushed the v3.0.0 tag BEFORE attempting the npm publish, which
failed. That left a tag with nothing behind it, which then permanently blocks
every future retry -- the check job's "does this tag exist" test reports the
version as already released, so the pipeline no-ops without ever attempting
the publish again. Publish now runs before tagging, so a failed publish never
leaves a dangling tag. Also adds an explicit `npm whoami` step before publish,
since a bad NPM_TOKEN otherwise surfaces only as an opaque "exit code 1" -- and
per actions/setup-node#1551, setup-node writes an _authToken line to .npmrc
even when the token is empty, which makes npm treat auth as "already
configured" and skip OIDC discovery rather than falling back to it.
The stale v3.0.0 tag from the failed run is deleted (locally and on origin) so
the next attempt starts clean.
0 commit comments