Repository navigation
ci: bump actions/setup-node and Node version - #17
Merged
Merged
Conversation
Bump actions/setup-node to SHA-pinned v7.1.0. v1-v4 run on the deprecated node12/16/20 action runtimes; v5+ run on node24. Also pin node-version '22' (it relied on the runner's default Node).
v1.8.0 runs the new binary foundryup through bash and fails with 'cannot execute binary file'; v1.9.0+ handles the Rust installer.
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.
Bump actions/setup-node to SHA-pinned v7.1.0. v1-v4 run on the deprecated node12/16/20
action runtimes; v5+ run on node24.
Also pin node-version '22' (it relied on the runner's default Node).
Also bumps foundry-toolchain v1.8.0 -> v1.9.1 (SHA-pinned): v1.8.0 fails on the new binary
foundryup installer ('cannot execute binary file'), which broke CI independent of this change.