ci: use Node 24 latest for OIDC release runners

[omegent-app]

Summary

The Changesets version job failed before publish:

npm error engine Not compatible with your version of node/npm: npm@12.0.1
npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error notsup Actual:   {"node":"v24.14.1","npm":"11.11.0"}

npm install -g npm@latest pulled npm 12, which needs Node ≥ 24.15. The runner is on Node 24.14 with npm 11.11.0, which already satisfies OIDC trusted publishing (≥ 11.5.1).

This PR updates .github/release.oidc.yaml (template) to remove that upgrade step.

Maintainer action (bot cannot push workflow files)

After merge, or immediately on main:

# delete these 3 lines from .github/workflows/release.yaml:
#      - name: Ensure npm supports OIDC trusted publishing
#        run: npm install -g npm@latest && npm --version

# or re-copy the fixed template:
cp .github/release.oidc.yaml .github/workflows/release.yaml
git add .github/workflows/release.yaml
git commit -m "ci: remove npm@latest upgrade breaking OIDC publish"
git push

Then re-run the failed Changesets workflow (or wait for the push).

Test plan

• Live release.yaml no longer runs npm@latest upgrade
• Version job reaches publish
• Log shows OIDC path: No NPM_TOKEN found, but OIDC is available - using npm trusted publishing

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/effect-app/libs/@effect-app/cli@825

effect-app

npm i https://pkg.pr.new/effect-app/libs/effect-app@825

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-codegen-model@825

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-shared-config@825

@effect-app/infra

npm i https://pkg.pr.new/effect-app/libs/@effect-app/infra@825

@effect-app/vue

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue@825

@effect-app/vue-components

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue-components@825

commit: aeeaf9f

[patroza]

@omegent instead of the workaround, maybe get the runners up to latest 24.x versions?

[omegent-app]

Agreed — better fix is bump the runner Node line, not drop the npm upgrade.

Root cause: npm@12 requires Node ^24.15 / ^22.22. The release job pinned 24.14, so npm i -g npm@latest failed with EBADENGINE.

Change on this PR (.github/release.oidc.yaml):

• node-version: 24 → latest 24.x (currently 24.18.x; satisfies npm 12’s engine)
• keep npm install -g npm@latest for a current CLI (OIDC needs ≥ 11.5.1)

CI already uses node-version: latest; release was the outlier on a stale patch pin.

After merge, re-apply the live workflow (bot still can’t write under .github/workflows/):

cp .github/release.oidc.yaml .github/workflows/release.yaml
git add .github/workflows/release.yaml
git commit -m "ci: Node 24 latest + npm@latest for OIDC publish"
git push

[omegent-app]

Agreed — aligning the release workflow with latest Node 24.x (CI already uses latest) and restoring the npm upgrade.

grok-4.5 · 1m 1s