Foundry’s nightly release dated November 13, 2026 includes changes to Tempo configurable-account handling, Forge test output and counterexamples, and EVM test performance. The source lists software changes, not evidence of adoption or deployment by users. The release notice was published at 15:10 UTC+8.
Tempo and Cast
- Cast and Forge gained detection of Tempo configurable-account senders (#18410, @mablr). Tempo configurable-account signing was added to cheatcodes (#18408, @mablr), and Cast gained access-key authorization for those accounts (#18407, @mablr).
- Cast fixes cover configurable-account digest help and raw WebAuthn signatures (#18421, @stevencartavia), retention of 7702 authorizations while resolving a fee token (#18428, @stevencartavia), and Tempo lane nonces and
--authhandling on account-abstraction transactions (#18426, @mablr). - Other Cast changes decode Safe v1.3.0 result events (#18425, @0xKarl98), verify Safe transaction hashes locally (#18418, @0xKarl98), and stop using
CHAINinwallet newwithout opt-in (#18420, @stevencartavia).
Testing and execution
Forge can now minimize stateless fuzz counterexamples (#18391, @stevencartavia). Fixes keep live logs out of JSON output (#18419, @stevencartavia), retain invariant-test shrink progress at the deadline (#18414, @stevencartavia), and limit test discovery to project paths (#18424, @0xKarl98).
The release also cuts per-opcode and per-call overhead in EVM tests (#18412, @figtracer) and prefetches state for simulated calls on forks (#18247, @figtracer). EVM fixes clear storage for committed creates (#18359, @stevencartavia), while a cheatcode fix preserves writes made after reverted restores (#18174, @stevencartavia).
Rounding out the nightly, fmt ignores blank lines when inlining bodies (#18422, @stevencartavia), and a symbolic-code refactor removes dead solver and ABI code (#18429, @stevencartavia).