Every workflow job sets up node-version: 23.x. Node.js 23 reached end of life on 2025-06-01, so CI builds, tests and publishes on an unsupported runtime. Node.js 24 is the active LTS release and satisfies the workspaces' engines.node >=23.0.0.
The pinned actions (actions/checkout, actions/setup-node, actions/cache and actions/upload-artifact at v4, peter-evans/repository-dispatch at v3) target the deprecated Node.js 20 action runtime. Every run logs a deprecation warning and GitHub forces them onto Node.js 24.
Done when: every workflow sets up Node.js 24.x; every action is pinned by commit SHA to its current major that runs on Node.js 24; and the full CI matrix passes. The publish job's OIDC setup must stay correct under setup-node v7, which no longer exports a placeholder NODE_AUTH_TOKEN.
Every workflow job sets up
node-version: 23.x. Node.js 23 reached end of life on 2025-06-01, so CI builds, tests and publishes on an unsupported runtime. Node.js 24 is the active LTS release and satisfies the workspaces'engines.node >=23.0.0.The pinned actions (
actions/checkout,actions/setup-node,actions/cacheandactions/upload-artifactat v4,peter-evans/repository-dispatchat v3) target the deprecated Node.js 20 action runtime. Every run logs a deprecation warning and GitHub forces them onto Node.js 24.Done when: every workflow sets up Node.js 24.x; every action is pinned by commit SHA to its current major that runs on Node.js 24; and the full CI matrix passes. The publish job's OIDC setup must stay correct under setup-node v7, which no longer exports a placeholder
NODE_AUTH_TOKEN.