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

deps: update foundry #9038

Merged
merged 1 commit into from
Jan 17, 2024
Merged

deps: update foundry #9038

merged 1 commit into from
Jan 17, 2024

Conversation

tynes
Copy link
Contributor

@tynes tynes commented Jan 17, 2024

Description

Updates foundry to the commit 9e2830d7f0566e0d00b1104eeaedd5032a4e556e.
Includes the vm.dumpState cheatcode implemented in foundry-rs/foundry#6827.
This will unblock the migration of the genesis generation to solidity to
improve the devex of the L2 contracts and allow us to delete a lot of
custom Go code as well as reduce flakes in CI due to not being able to
find the genesis.json.

Updates foundry to the commit `9e2830d7f0566e0d00b1104eeaedd5032a4e556e`.
Includes the `vm.dumpState` cheatcode implemented in foundry-rs/foundry#6827.
This will unblock the migration of the genesis generation to solidity to
improve the devex of the L2 contracts and allow us to delete a lot of
custom Go code as well as reduce flakes in CI due to not being able to
find the `genesis.json`.
@tynes tynes requested a review from refcell January 17, 2024 15:51
@refcell
Copy link
Contributor

refcell commented Jan 17, 2024

Just double checking local install works, one sec

@refcell
Copy link
Contributor

refcell commented Jan 17, 2024

Perfect

@refcell refcell added this pull request to the merge queue Jan 17, 2024
Merged via the queue into develop with commit 0b7e171 Jan 17, 2024
66 checks passed
@refcell refcell deleted the deps/forge-latest branch January 17, 2024 16:47
tynes added a commit that referenced this pull request Jan 17, 2024
The foundry install script uses `jq` so we must install `jq` as early
as possible in `ci-builder` to ensure that its always present.

Follow up to #9042
which fixes the broken build from #8920.

I don't think that #8920 broke the fix in this commit so perhaps the
build was broken longer than we thought? Either way, we need new forge
version in CI that was introduced in #9038
so we need a successful build of `ci-builder`.
github-merge-queue bot pushed a commit that referenced this pull request Jan 17, 2024
The foundry install script uses `jq` so we must install `jq` as early
as possible in `ci-builder` to ensure that its always present.

Follow up to #9042
which fixes the broken build from #8920.

I don't think that #8920 broke the fix in this commit so perhaps the
build was broken longer than we thought? Either way, we need new forge
version in CI that was introduced in #9038
so we need a successful build of `ci-builder`.
dshiell pushed a commit to polymerdao/optimism-dev that referenced this pull request Jan 22, 2024
Updates foundry to the commit `9e2830d7f0566e0d00b1104eeaedd5032a4e556e`.
Includes the `vm.dumpState` cheatcode implemented in foundry-rs/foundry#6827.
This will unblock the migration of the genesis generation to solidity to
improve the devex of the L2 contracts and allow us to delete a lot of
custom Go code as well as reduce flakes in CI due to not being able to
find the `genesis.json`.
dshiell pushed a commit to polymerdao/optimism-dev that referenced this pull request Jan 22, 2024
The foundry install script uses `jq` so we must install `jq` as early
as possible in `ci-builder` to ensure that its always present.

Follow up to ethereum-optimism#9042
which fixes the broken build from ethereum-optimism#8920.

I don't think that ethereum-optimism#8920 broke the fix in this commit so perhaps the
build was broken longer than we thought? Either way, we need new forge
version in CI that was introduced in ethereum-optimism#9038
so we need a successful build of `ci-builder`.
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 this pull request may close these issues.

2 participants