ci: bump actions/setup-node to v7 (#32) - #77
Merged
Conversation
Every other action is already pinned at its latest major: checkout v7, configure-pages v6, upload-pages-artifact v5, deploy-pages v5, action-gh-release v3, lychee-action v2, create-issue-from-file v6. Supersedes the github-actions group PR textrefs#32, which targets `main` and would otherwise be reverted by the next staging squash.
There was a problem hiding this comment.
Pull request overview
Updates GitHub Actions workflows to use actions/setup-node@v7 (from v6) as the last outstanding CI dependency bump ahead of the v0.1.0 release process.
Changes:
- Bump
actions/setup-nodefromv6→v7in the validation workflow. - Bump
actions/setup-nodefromv6→v7in the Pages build/deploy workflow. - Bump
actions/setup-nodefromv6→v7in the release workflow.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/validate.yml |
Uses actions/setup-node@v7 for Node 24 + npm cache during validation. |
.github/workflows/pages.yml |
Uses actions/setup-node@v7 for Node 24 + npm cache during site build prior to Pages deploy. |
.github/workflows/release.yml |
Uses actions/setup-node@v7 for Node 24 + npm cache before building/attaching dump artifacts. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Aug 12, 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.
Last outstanding dependency bump before
v0.1.0.actions/setup-nodev6 → v7 acrossvalidate.yml,pages.ymlandrelease.yml.Every other action is already pinned at its latest major:
checkoutv7,configure-pagesv6,upload-pages-artifactv5,deploy-pagesv5,action-gh-releasev3,lychee-actionv2,create-issue-from-filev6.Why this targets
staging, notmainDependabot's #32 targets
main, which only moves at release time. Anything merged there that is not also onstaginggets reverted by the nextstaging → mainsquash — the squash applies staging's tree against a merge base that predates the bump. Landing it here means it reachesmainthrough #4 like everything else, and #32 can be closed rather than merged.Same reasoning applies to the ten npm dependabot PRs superseded by #73.
Self-testing
The
datacheck on this PR runsvalidate.ymlwith the bumped action, so a green run is direct evidence the upgrade works.release.ymlcannot be exercised before the tag; it uses the same three steps asvalidate.yml(checkout, setup-node,npm ci), so the risk of it behaving differently is low.Closes #32. Part of #68.