Update Node version to 24 in CI workflows#4094
Merged
Merged
Conversation
Copilot created this pull request from a session on behalf of
jonrohan
June 15, 2026 17:35
View session
|
jonrohan
added
the
skip changeset
Contributor
There was a problem hiding this comment.
Pull request overview
Updates GitHub Actions CI workflows to run on Node.js 24 instead of 20, aligning all CI jobs (including Playwright-based visual/accessibility runs and CodeQL) with a consistent Node runtime.
Changes:
- Bumped
actions/setup-nodenode-versionfrom20→24across CI workflows. - Completed the remaining
release.ymlstep that was still on Node 20 sorelease.ymlis fully on Node 24.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/test-visual.yml | Update CI Node version to 24 for Playwright visual tests. |
| .github/workflows/test-system.yml | Update CI Node version to 24 for system test job setup/build steps. |
| .github/workflows/test-selectors.yml | Update CI Node version to 24 for selector build/test workflow. |
| .github/workflows/test-lib.yml | Update CI Node version to 24 for library test workflow builds. |
| .github/workflows/test-components.yml | Update CI Node version to 24 for component test workflow builds. |
| .github/workflows/test-accessibility.yml | Update CI Node version to 24 for Playwright accessibility tests. |
| .github/workflows/static-files.yml | Update CI Node version to 24 for static file generation workflow. |
| .github/workflows/release.yml | Update remaining release job Node version to 24. |
| .github/workflows/codeql-analysis.yml | Update CI Node version to 24 for CodeQL JavaScript analysis job. |
Copilot's findings
- Files reviewed: 9/9 changed files
- Comments generated: 1
Comment on lines
24
to
27
| - uses: actions/setup-node@v5 | ||
| with: | ||
| node-version: 20 | ||
| node-version: 24 | ||
| cache: "npm" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
Bump
node-versionfrom20to24across all CI workflows for consistency with the already-updatedrelease.ymlsteps.Updated workflows:
test-system.ymltest-lib.ymltest-selectors.ymltest-components.ymltest-accessibility.ymlstatic-files.ymltest-visual.ymlcodeql-analysis.ymlrelease.yml(remaining step on 20)Integration
No production code changes. CI-only.
Risk Assessment
What approach did you choose and why?
Single-value
node-versionreplacement to keep all jobs on a consistent runtime.release.ymlalready pinned two steps to 24; this aligns the remainder.Anything you want to highlight for special attention from reviewers?
Confirm Node 24 is acceptable for all jobs, particularly Playwright-based visual/accessibility runs.
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.