Foundry v1.0.0

Read the announcement post for more info about Foundry's first stable release.

Foundry's first stable release! After over a year of building and contributions from 271 builders, it's time to signal Foundry's stability and robustness to the world.

What does Foundry v1 bring?

We've been fixing bugs for the past few months, and in the meantime we decided to make some breaking changes to several cheatcodes, which will help you write more strict and correct tests. We've also deprecated several features, which are still available, but are now on track for future removal. See the deprecated features and breaking changes section of the migration guide.

Aside from this, Foundry is still the same Ethereum development toolkit you know!

Will my tests break? How do I migrate?

It's possible that this update might break some of your tests, as the expect (expectCall, expectEmit and expectRevert) cheatcodes are now more strict. We've prepared a migration guide to make the process as painless as possible.

How do I update to v1?

You'll need to reinstall foundryup (see the install instructions in the book). After this, simply do foundryup, and you will download the latest stable release.

If you'd like to return to the latest nightly, do foundryup --legacy.

Will my CI break?

Not for now. You will need to manually update it to v1, by changing the version input to v1.0.0. We'll be giving a grace period for pinning the CI to stable, before it's the default.

What does this mean for Foundry's release cadence?

This means that there will be no more nightlies—and official stable releases will be a bit more spread out rather than having daily updates. Development speed will still stay the same, and we'll adjust release cadence depending on community feedback.

What's next?

We're looking to improve several core features of Foundry, such as scripting, forge's formatter, several JSON cheatcodes, and heavily improve internals to leverage new next-gen tools such as Alloy and Reth's internals.

We're also making a commitment to improving the foundry book through new content, tutorials, and better documentation. Our objective is to not only have best-in-class documentation for Foundry, but also to make it a resource where new Solidity developers can use as a reference and learn best practices on testing, deploying and analyzing smart contracts.

Important links

• Migration guide
• Blog post
• Telegram Dev Chat
• Telegram Support Channel