Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bootstrap.sh requires out of date version of Foundry #10977

Closed
cryptoryda opened this issue Dec 30, 2024 · 2 comments · Fixed by #10995
Closed

bootstrap.sh requires out of date version of Foundry #10977

cryptoryda opened this issue Dec 30, 2024 · 2 comments · Fixed by #10995

Comments

@cryptoryda
Copy link

cryptoryda commented Dec 30, 2024

PROBLEM

While running "./bootstrap.sh full" on a Debian 12.8 VM without foundryup installed, I receive the error
ERROR: Toolchain incompatibility. We encourage use of our dev container.
See build-images/README.md.
forge not in PATH or incorrect version (requires 25f24e677a6a32a62512ad4f561995589ac2c7dc).
Installation: https://book.getfoundry.sh/getting-started/installation
curl -L https://foundry.paradigm.xyz | bash
foundryup -v nightly-25f24e677a6a32a62512ad4f561995589ac2c7dc

This is as expected, but after following the installation instructions the actual version installed is 5a8bd893eeeeb9489ea66dd52a02eeaa580e3af0.
Also, "foundryup -v nightly-25f24e677a6a32a62512ad4f561995589ac2c7dc" returns "foundryup: warning: unknown option: -v"

@cryptoryda
Copy link
Author

A fix for this can be found here #10978.

@Maddiaa0
Copy link
Member

Maddiaa0 commented Jan 2, 2025

Thank you for making this issue, i see that foundryup has a breaking change and has replaces -v with -i instead.

We use a locked commit of foundry so that all of our CI and local dev environments are running with stable versions we know not to have bugs.

I think the solution we should run for is to run foundryup -i on the locked commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants