Repository navigation
ci: use actions/setup-node - #747
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 52 minutes. View limit details
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Configure tools and install dependencies .github/actions/setup/action.yml |
The action uses separate pinned pnpm and Node setup steps. Node setup uses the configured version, enables pnpm caching, and sets the npm registry URL. A Bash step runs pnpm install. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Bug fix
Possibly related PRs
- prosekit/meowdown#733: This PR updates the same setup action. The current change replaces the
pnpm/setupimplementation updated by that PR.
Merge Risk: 
Minimal · previous review 3bfba
-
The setup action resolves pnpm 11.28.6 before enabling Node caching and installs dependencies from the repository root.
Pre-merge checks: 
4
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Comment @coderabbitai help to get the list of available commands.
commit: |
Coverage Report
File CoverageNo changed files found. |
|
Deployment failed for project meowdown with the following error: Learn More: https://vercel.com/ocavues-projects?upgradeToPro=build-rate-limit |
Replace
pnpm/setupwithpnpm/action-setup+actions/setup-nodein the shared setup action, sincepnpm/setuphas been causing CI failures. This reverts the approach from #538, using the latest pinned versions (pnpm/action-setup v6.1.0, actions/setup-node v7.1.0).Summary by CodeRabbit