Merged
Conversation
Piyush-85
reviewed
Apr 6, 2026
Piyush-85
approved these changes
Apr 6, 2026
7 tasks
ankita10119
added a commit
that referenced
this pull request
Apr 6, 2026
…ion (#2774) ### 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 bum**p 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: #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](https://github.com/auth0/open-source-template/blob/master/GENERAL-CONTRIBUTING.md) * [ ] I have read the [Auth0 Code of Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md) * [ ] All code quality tools/guidelines have been run/followed * [ ] All relevant assets have been compiled
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
Changed
Deprecated
Fixed