Foundry’s November 13, 2026 nightly release lists changes to Tempo account handling, cast, forge and testing internals. This is a release changelog, not evidence of wider adoption. The release was reported on November 13, 2026, at 15:10 (UTC+08:00).
Tempo accounts and cast
castandforgedetect Tempo configurable account senders (#18410, @mablr). Cheatcodes add Tempo configurable account signing (#18408, @mablr).castcan authorize access keys as a Tempo configurable account (#18407, @mablr). Its configurable-account digest help and handling of raw WebAuthn signatures were fixed (#18421, @stevencartavia).- Tempo fee-token resolution now keeps EIP-7702 authorizations (#18428, @stevencartavia).
castuses Tempo lane nonces and carries--authon account-abstraction transactions (#18426, @mablr). castfixes decoding of Safe v1.3.0 result events (#18425, @0xKarl98) and verifies Safe transaction hashes locally (#18418, @0xKarl98).cast wallet newignoresCHAINunless opted in (#18420, @stevencartavia).
Testing, execution and formatting
forgekeeps live logs out of JSON output (#18419, @stevencartavia), minimizes stateless fuzz counterexamples (#18391, @stevencartavia) and limits test discovery to project paths (#18424, @0xKarl98). Invariant shrinking retains its progress at the deadline (#18414, @stevencartavia).- Changes reduce per-opcode and per-call test overhead (#18412, @figtracer) and prefetch state for simulated calls on forks (#18247, @figtracer).
- EVM execution clears storage for committed contract creations (#18359, @stevencartavia). Cheatcodes retain writes made after reverted restores (#18174, @stevencartavia).
fmtignores blank lines when inlining bodies (#18422, @stevencartavia). A symbolic-code refactor removes unused solver and ABI code (#18429, @stevencartavia).