You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, Foundry uses Scarb 2.7.0 in tool-versions. Upgrading to 2.8.0 causes a lot of runtime errors in tests.
However a standard users' "create - declare - deploy" pipeline works fine.
The text was updated successfully, but these errors were encountered:
Why do we need to do this? I believe we don't want to upgrade for every version of scarb, we want to keep it as low as possible for compatibility reasons (when it's possible)
<!-- Reference any GitHub issues resolved by this PR -->
Related to #2426
## Introduced changes
<!-- A brief description of the changes -->
- Removed running `init_new_project` and `init_new_project_from_scarb`
tests for Scarb `2.8.1`. These tests are executed in the job
`test-forge-e2e` with Scarb `2.7.0`
- Enabled running coverage test on CI
At the moment, Foundry uses Scarb
2.7.0
intool-versions
. Upgrading to2.8.0
causes a lot of runtime errors in tests.However a standard users' "create - declare - deploy" pipeline works fine.
The text was updated successfully, but these errors were encountered: