Update GitHub Actions runtimes - #8
Merged
Merged
Conversation
Bigsticktw
marked this pull request as ready for review
July 29, 2026 06:42
This was referenced Jul 29, 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
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.
What changed
actions/checkoutfrom v4 to v7.actions/setup-nodefrom v4 to v7.actions/configure-pagesfrom v5 to v6.actions/upload-pages-artifactfrom v3 to v5.actions/deploy-pagesfrom v4 to v5.Why
The first production runs succeeded but GitHub warned that the older action releases target the deprecated Node.js 20 runtime. These versions are the current major releases reported by the official GitHub release API on 2026-07-29.
Verification