chore(ci): bump Node 20 actions to Node 24 and SHA-pin - #4
Merged
Conversation
Replaces mutable tags with full commit SHAs (per CI/CD hardening policy) and upgrades each action to the latest Node 24-based release, resolving GitHub's Node 20 deprecation annotation (forced switch 2026-06-02, removal 2026-09-16). - actions/checkout: @v4 → @de0fac2… # v6.0.2 - denoland/setup-deno: @v2 → @667a34c… # v2.0.4 - stefanzweifel/git-auto-commit-action: @v5 → @04702ed… # v7.1.0 - actions/configure-pages: @v5 → @45bfe01… # v6.0.0 - actions/upload-pages-artifact: @V3 → @fc324d3… # v5.0.0 - actions/deploy-pages: @v4 → @cd2ce8f… # v5.0.0 The workflow uses only documented, stable inputs (ref, fetch-depth, path, commit_message, status_options) that are unchanged across these major version bumps. Closes #3 InfoSec: dependency upgrade to restore supported runtime before EOL; SHA pinning prevents surprise changes from mutable-tag resolution. No new permissions, secrets, or input surface.
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
1 participant
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
@v4,@v5, etc.) inupdate-profile-readme.ymlwith full commit SHAs + version comments, per CI/CD hardening policyChanges
actions/checkout@v4@de0fac2… # v6.0.2denoland/setup-deno@v2@667a34c… # v2.0.4stefanzweifel/git-auto-commit-action@v5@04702ed… # v7.1.0actions/configure-pages@v5@45bfe01… # v6.0.0actions/upload-pages-artifact@v3@fc324d3… # v5.0.0actions/deploy-pages@v4@cd2ce8f… # v5.0.0Compatibility note
The workflow uses only documented, stable inputs —
ref,fetch-depth,path,commit_message,status_options— and none changed across these major version bumps.git-auto-commit-actiondroppedskip_fetch/skip_checkout/create_branchin v6 and restored them in v7; this workflow uses none of those.Test plan
action.ymlUpdate Profile READMEworkflow runs green on this PR (build + commit + Pages deploy)rickcogley.github.io/rickcogley) still serves correctlyInfoSec: dependency upgrade to restore supported runtime before EOL; SHA pinning prevents surprise changes from mutable-tag resolution. No new permissions, secrets, or input surface.