ci: run workflows on Node 22 (required by @vscode/vsce 4) - #113
Conversation
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughBoth CI workflows now use Node.js 22 instead of Node.js 20. The build workflow applies Node.js 22 to installation, build, test, and VSIX packaging steps. ChangesNode.js 22 CI Update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
@vscode/vsce 4.0.0 (#112) raises its Node.js baseline to 22 (microsoft/vscode-vsce#1308). CI and the publish workflow still pin Node 20, so the packaging step would run on an unsupported runtime. This moves both workflows to Node 22 ahead of merging #112.
Summary by CodeRabbit