Repository navigation
ci: bump foundry-toolchain to v1.9.1 (foundryup is now a binary) - #263
Merged
Merged
Conversation
foundry-toolchain v1.8.0 runs the foundryup installer through bash, but foundryup ships as a binary now, so every Install Foundry step fails with "cannot execute binary file". contracts-ci has been red since September for that reason alone; the oracle-poc CI and the keeper use the same step. v1.9.1 pinned by commit, as before.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
foundry-toolchain v1.8.0 runs the foundryup installer through bash, but foundryup ships as a binary now, so every Install Foundry step fails with "cannot execute binary file". contracts-ci has been red since September for that reason alone; the oracle-poc CI and the keeper use the same step.
v1.9.1 pinned by commit, as before.
Summary
What changed, and which issue does it address?
Fixes #
Scope
Verification
I ran:
Result:
Safety checklist
.envfiles, private keys, wallet seeds, webhook URLs, API tokens, or private datasets.Valuation notes
If this PR is intended to be considered in a monthly valuation round, summarize
the Git-visible artifact value in one or two sentences.
If the PR is not intended for a valuation round (e.g. drive-by docs fixes), leave this section as
n/a - not submitted for valuation.