Upgrade GitHub Actions for Node 24 compatibility#13895
Open
salmanmkc wants to merge 1 commit intomicrosoft:masterfrom
Open
Upgrade GitHub Actions for Node 24 compatibility#13895salmanmkc wants to merge 1 commit intomicrosoft:masterfrom
salmanmkc wants to merge 1 commit intomicrosoft:masterfrom
Conversation
salmanmkc
requested review from
Brian-Perkins,
OneBlue,
benhillis,
Copilot and
justus-camp-microsoft
Contributor
There was a problem hiding this comment.
Pull request overview
This PR proactively upgrades the actions/checkout action from v4 to v6 across all GitHub Actions workflows to ensure compatibility with Node 24, which will become the default runtime on GitHub Actions runners starting March 2026, before Node 20 reaches end-of-life in April 2026.
Key Changes
- Updated all instances of
actions/checkout@v4toactions/checkout@v6across 6 workflow files - Changes are purely version bumps with no functional modifications to workflow logic
- Maintains consistent action versions across all CI/CD workflows
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/new_issue_comment.yml |
Updated checkout action to v6 for issue comment processing workflow |
.github/workflows/new_issue.yml |
Updated checkout action to v6 for new issue processing workflow |
.github/workflows/modern-distributions.yml |
Updated checkout action to v6 for tar-based distribution validation workflow |
.github/workflows/issue_edited.yml |
Updated checkout action to v6 for edited issue processing workflow |
.github/workflows/documentation.yml |
Updated checkout action to v6 for documentation build and deployment workflow |
.github/workflows/distributions.yml |
Updated checkout action to v6 for distribution validation workflow |
OneBlue
reviewed
Jan 6, 2026
| with: | ||
| issue: "${{ github.event.issue.number }}" | ||
| previous_body: "${{ github.event.changes.body.from }}" | ||
| name: Process edited issue |
Collaborator
There was a problem hiding this comment.
Not sure what's going on with the diff in this file, maybe the line endings have been changed ?
Would you mind undoing this to preserve history on this file and .github/workflows/new_issue_comment.yml ?
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
3 participants
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.
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/checkoutv6Context
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.