CI: migrate workflows to setup-node v4#38
CI: migrate workflows to setup-node v4#38eeemmmmmm wants to merge 1 commit intoreclaimprotocol:mainfrom
Conversation
WalkthroughThe GitHub Actions workflow for publishing to NPM was updated to use version 4 of the Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.github/workflows/publish.yaml (1)
24-24: Upgradeactions/setup-nodestep to v4
Switching toactions/setup-node@v4aligns with the PR objective to future-proof workflows. v4 retains support for theregistry-urlinput, but verify that no new required inputs (e.g.,always-auth) are needed for your publish process.Consider adding npm cache support to speed up installs:
uses: actions/setup-node@v4 with: node-version: ${{ matrix.node-version }} registry-url: 'https://registry.npmjs.org' cache: 'npm'
Bumps setup-node to v4 for future-proofing against runner updates. Workflows compile the same. Reference: https://github.com/actions/setup-node/releases/tag/v4.0.0
Summary by CodeRabbit