Upgrade GitHub Actions for Node 24 compatibility #3152
Conversation
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
There was a problem hiding this comment.
Pull request overview
Updates GitHub Actions workflow dependencies to newer major versions to maintain compatibility as GitHub Actions runners transition from Node 20 to Node 24.
Changes:
- Bump
actions/upload-artifactfromv5tov6in the PR checks workflow. - Bump
actions/checkoutandactions/setup-nodefromv4tov6in the npm package workflow. - Bump
actions/cachefromv4tov5in the node modules cache workflow.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/pr.yml |
Upgrades artifact upload action to v6 for Node 24 compatibility. |
.github/workflows/npm-package.yml |
Upgrades checkout and Node setup actions to v6. |
.github/workflows/ensure-node-modules-cache.yml |
Upgrades cache action to v5 on Linux and Windows jobs. |
| - name: Upload simulation output | ||
| if: always() | ||
| uses: actions/upload-artifact@v5 | ||
| uses: actions/upload-artifact@v6 | ||
| with: | ||
| name: simulation-output-linux-${{ github.run_attempt }} |
There was a problem hiding this comment.
This PR targets Node 24 runner compatibility, but this workflow still uses actions/cache/restore@v4 earlier in the file (e.g., around lines 31/101/191). That appears inconsistent with the upgrade goal and could leave this workflow relying on an action major that may not be Node 24 compatible. Consider upgrading those cache steps to the corresponding v5 action(s) as well, or clarify in the PR description why they are intentionally left on v4.
2 participants
Summary
Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.
Changes
actions/cachev4v5actions/checkoutv4v6actions/setup-nodev4v6actions/upload-artifactv5v6Context
Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.
Why this matters
Security Note
Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.
Testing
These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.