Repository navigation
ci: use node-version-file in setup-vp actions - #3367
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Use the repository Node.js version .github/workflows/autofix.yml, .github/workflows/chromatic.yml, .github/workflows/ci.yml, .github/workflows/deploy-canary.yml, .github/workflows/lunaria.yml, .github/workflows/release-pr.yml, .github/workflows/release-tag.yml |
The workflow setup steps now read the Node.js version from .node-version instead of selecting lts/*. |
Suggested reviewers: ghostdevv
Priority:
Merge Risk: 
Minimal · previous review 2f31a
-
The workflows now select Node.js from the repository version file rather than following the latest LTS release. No actionable merge-blocking issue was found; the change is ready to merge subject to normal workflow checks.
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.
node-version-file in setup-vp actions
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
I think the lunaria workflow is failing because it's using |
🔗 Linked issue
None
🧭 Context
CI currently sets
node-versiontolts/*Yesterday Node 26 became the new LTS version
This broke CI because
better-sqlite3dependency doesn't build with Node 26📚 Description
Updates
setup-vpactions to usenode-version-fileinstead ofnode-versionsince we already have a.node-versionfile