Repository navigation
chore: Bump GitHub Actions to their Node.js 24 versions - #23
Merged
Merged
Conversation
Generated-by: termag
kinyoklion
approved these changes
Nov 17, 2026
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.


Summary
GitHub has deprecated the Node.js 20 runtime for JavaScript actions, and workflows in this repository print a deprecation warning on every run. This PR bumps each action that runs on Node.js 20 or older to its latest major release, which runs on Node.js 24. Tag pins stay tag pins. SHA pins move to the SHA of the new release, with a version comment.
actions/checkout08eba0b (v4),v43d3c42e (v7.0.1),v7actions/setup-nodev4v7None of the bumps change the inputs this repository passes.
Behavior changes to know about:
actions/checkoutv6 and later store the persisted credentials in a separate file under$RUNNER_TEMP, not in.git/config.actions/setup-nodev5 and later turn on dependency caching whenpackage.jsonhas apackageManagerfield. v6 and later do this only for npm.Opened from termag
Note
Overview
Upgrades GitHub Actions that were running on the deprecated Node.js 20 runtime to their v7 releases (Node.js 24), which should stop deprecation warnings on workflow runs.
In Verify Hello App,
actions/checkoutandactions/setup-nodemove from v4 to v7. In Dependency Scan, both jobs’actions/checkoutpins jump from the v4 commit SHA to v7.0.1’s SHA (comment updated). Workflow inputs and step order are unchanged.Worth noting for reviewers: newer
checkoutversions persist credentials outside.git/config, and newersetup-nodemay enable dependency caching whenpackage.jsondeclares apackageManager.Reviewed by Cursor Bugbot for commit f5d27e4. Bugbot is set up for automated code reviews on this repo. Configure here.