chore: upgrade node to 24 while releasing#13639
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the npm release workflow to use Node.js 24 during publishing, aiming to avoid release failures related to the npm CLI promise-retry issue referenced in the PR description.
Changes:
- Override the Node.js version used by the
./.github/actions/pnpm/setupcomposite action to24in the npm release job.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
📦 Binary Size-limit
🎉 Size decreased by 8.34KB from 49.35MB to 49.34MB (⬇️0.02%) |
Rsdoctor Bundle Diff AnalysisFound 6 projects in monorepo, 6 projects with changes. 📊 Quick Summary
📋 Detailed Reports (Click to expand)📁 popular-libsPath:
📁 react-10kPath:
📁 react-1kPath:
📁 romePath:
📁 react-5kPath:
📁 ui-componentsPath:
Generated by Rsdoctor GitHub Action |
Merging this PR will degrade performance by 1.11%
Performance Changes
Comparing Footnotes
|
Summary
release failed because of promise-retry, seems that can be resolved by upgrading node to v24
see npm/cli#9151
Related links
Checklist