fix: bump Node.js publish version to 22.23.1 to unblock npm@12 release

[ankita10119]

Changes

Bumps the Node.js version used in the release workflow from 22.22.1 to 22.23.1.

Why: npm@latest recently released v12.0.0, which requires Node ^22.22.2 at minimum. The workflow was pinned to 22.22.1 (one patch behind) as a temporary workaround for a Node.js regression (nodejs/node#62425) where the bundled npm was missing the promise-retry module. That regression has since been fixed in 22.22.3+, making it safe to bump the pin and unblock releases.

No SDK code, public API, or functionality is affected — this is a CI-only change.

References

• nodejs/node#62425 — upstream Node.js regression (closed/fixed)

Testing

This change can be verified by triggering the release workflow and confirming the npm install -g npm@latest step completes successfully on Node 22.23.1.

• This change adds unit test coverage
• This change adds integration test coverage

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.62%. Comparing base (c8b476c) to head (8748017).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1366   +/-   ##
=======================================
  Coverage   89.62%   89.62%           
=======================================
  Files         428      428           
  Lines       19886    19886           
  Branches     9757     9757           
=======================================
  Hits        17823    17823           
  Misses       2063     2063           

Flag	Coverage Δ
alltests	89.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.