Migrate Actions off Node 20 and pin to commit SHAs#2
Merged
Conversation
pyshx
force-pushed
the
migrate-actions-node24
branch
from
bd2808f to
8513477
Compare
See villagesql/villagesql-server#616 (migrate GitHub Actions off the deprecated Node 20 runtime).
pyshx
force-pushed
the
migrate-actions-node24
branch
from
8513477 to
8e4d958
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
GitHub is forcing Node 20 actions to Node 24 on 2026-06-16 (villagesql/villagesql-server#616).
actions/checkoutv4 → v6.0.3 (Node 20 → 24), pinned to its commit SHAcontributor-assistant/github-actionpinned to its v2.6.1 SHA (its latest release is still Node 20; no Node 24 build exists yet, so it is pinned to an immutable ref rather than bumped)The C++ build is delegated to
villagesql/extension-actions/cpp@main; its own Node 20upload-artifactis fixed in that repo (separate PR).SHAs were resolved from each action's release tag. Validated with
actionlint.