Repository navigation
bump github actions, use node 24 - #133
Conversation
* actions/checkout to v7 * actions/cache to v6 * actions/setup-node to v7 * actions/upload-artifact to v7 * nick-fields/retry to v4 * softprops/action-gh-release to v3
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (5)
Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe pull request updates GitHub Actions versions in setup, validation, integration-test, and release workflows. Existing test matrices, commands, retry settings, and deployment triggers remain unchanged. ChangesGitHub Actions version updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The action upgrades preserve the cited checkout behavior, with no concrete merge-blocking regression identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the workflow trail Comment |
Workflows gave a warning:
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, nick-fields/retry@v3As we are being forced to run on node 24 anyway, might as well update the actions.
packageManagerfield. We setcache: 'npm'explicitly, so nothing changes for us.archive: falsefor unzipped single-file uploads, which we don't use. We are going to use this later though as we are now uploading the artifiact after a release but this contains all our development files.Summary by CodeRabbit