fix(release): revert v14.3.0 and fix release pipeline Node.js regression

[ankita10119]

Changes

The v14.3.0 release was triggered via PR #2773 but failed in CI before npm publish completed. The version bump was merged to master but the package was never actually published to npm, leaving master in an inconsistent state with a version number that doesn't exist on the registry.

Revert v14.3.0 version bump

Reverts package.json, package-lock.json, .version, README.md, and CHANGELOG.md back to 14.2.5. Since 14.3.0 was never published to npm, the next successful release will use 14.3.0 again, this revert simply clears the failed release state so the release tooling can re-bump cleanly.

Pin Node.js to 22.22.1 in release.yml

The root cause of the release failure: Node.js 22.22.2 (the version currently resolved by node-version: 22 on the latest GitHub Actions runner images) ships with a broken bundled npm that is missing the promise-retry internal module. This causes the npm install -g npm@11 step to fail with Cannot find module 'promise-retry'.

This is a confirmed upstream regression tracked at nodejs/node#62425. Pinning to 22.22.1 is the recommended temporary workaround until a fixed patch is released upstream, at which point node-version: 22 can be restored.

References

• Failed release: Release v14.3.0 #2773
• Node.js regression: nodejs/node#62425

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed
• All relevant assets have been compiled