Multiple breaking changes will occur so Semver can be followed as soon as Foundry 1.0 is released. They will be listed here, along with the updates needed for your projects.
If you need a stable Foundry version, we recommend using the latest pinned nightly of May 2nd, locally and on your CI.
To use the latest pinned nightly locally, use the following command:
foundryup --version nightly-e15e33a07c0920189fc336391f538c3dad53da73
To use the latest pinned nightly on your CI, modify your Foundry installation step to use an specific version:
- name: Install Foundry
uses: foundry-rs/foundry-toolchain@v1
with:
version: nightly-e15e33a07c0920189fc336391f538c3dad53da73
- expectEmit will now only work for the next call.
- expectCall will now only work if the call(s) are made exactly after the cheatcode is invoked.
- expectRevert will now work if the next call does revert, instead of expecting a revert during the whole test.
- This will very likely break your tests. Please make sure that all the calls you expect to revert are external, and if not, abstract them into a separate contract so that they can be called externally and the cheatcode can be used.
-m, the deprecated alias for--mtor--match-test, has now been removed.- startPrank will now override the existing prank instead of erroring.
- precompiles will not be compatible with all cheatcodes.
- The difficulty and prevrandao cheatcodes now fail if not used with the correct EVM version.
- The default EVM version will be Shanghai. If you're using an EVM chain which is not compatible with EIP-3855 you need to change your EVM version. See Matt Solomon's thread for more information.
- Non-existent JSON keys are now processed correctly, and
parseJsonreturns non-decodable empty bytes if they do not exist. foundry-rs/foundry#5511