[claude]

Requested by Samuel Attard · Slack thread

The release job in release.yml moves off end-of-life Node 20 to Node 22.x, matching .nvmrc, the test matrix and engines (>=22.12.0); semantic-trusted-release still brings its own Node 24 for npm publishing. The floating setup-node step now sets check-latest: true.

---

Generated by Claude Code

[claude]

I reviewed this PR and found no new bugs. It's a small change, but it touches the release workflow and the CODEOWNERS file assigns this path to the ecosystem working group, so a maintainer should still look at it.

What was reviewed:

• The Setup Node.js step in .github/workflows/release.yml: node-version goes from 20.x to 22.x and check-latest: true is added. The action is still pinned to the same commit SHA.
• I checked that the new version matches the repo's other Node declarations. .nvmrc is 22.23.4 and engines is >=22.12.0, so a 22.x release runner satisfies both.

Extended reasoning...

The only change is one setup-node step in .github/workflows/release.yml. It moves the release job from Node 20.x to 22.x and adds check-latest: true, and the action stays pinned to the same SHA. No source, test or other config files change. The release workflow publishes to npm, which makes it the release path rather than an auth or crypto change. CODEOWNERS assigns all paths to a maintainer team, which is why a human review is suggested instead of approving.

[electron-npm-package-publisher]

🎉 This PR is included in version 3.0.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀