chore: bump to node.js 24 and enable oidc publishing

[mrcointreau]

Summary

• Bump Node.js version from 22 to 24 across all CI workflows
• Upgrade GitHub Actions to latest major versions
• Switch npm publishing from token-based auth (NPM_TOKEN) to OIDC-based auth with provenance

[iglosiggio]

Changes look good. The only question I have is moving from node 22 to node 24. node 22 will have support until April 2027 (it just finished active development on October of 2025). https://nodejs.org/en/about/previous-releases

Do you have any details on who we may leave behind with this change? (Or is it the idea to target node22 and use node24 as our runtime)

[mrcointreau]

@iglosiggio

The minimum supported Node version is still 20.11.1 (enforced via a runtime check in src/constants.ts), and the CI matrix continues to test against Node 20, 22 and 24, so no consumers should be left behind. This change is meant to only bump the Node version used for CI jobs like publishing and docs builds. The main motivation is enabling OIDC-based npm provenance which works with npm 11.5.1 only.

An alternative and safer approach would be to keep the current Node versions as they are and just update npm to 11.5.1 in the CI workflows.

[iglosiggio]

Thanks for the details!

[engineering-ci]

🎉 This PR is included in version 1.2.0-beta.29 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀