If you’re reviewing how Foundry handles contract tests or account transactions, the November 13, 2026 nightly release lists changes across forge, cast and the Ethereum Virtual Machine (EVM), which executes smart-contract code. The release was published at 15:10 (UTC+08:00). These are changelog entries, not claims that a workflow has been tested or that the release has seen wider adoption.
Accounts and transactions
castandforgegained detection of Tempo configurable-account senders (#18410, @mablr). Cheatcodes—Foundry’s test utilities—gained Tempo configurable-account signing (#18408, @mablr), andcastgained access-key authorization for those accounts (#18407, @mablr).castchanges cover configurable-account digest help and raw WebAuthn signatures (#18421, @stevencartavia); Tempo lane nonces and carrying--authon account-abstraction transactions (#18426, @mablr); and local verification of Safe transaction hashes (#18418, @0xKarl98). A nonce is a value used to distinguish transactions.- Other fixes address decoding Safe v1.3.0 result events (#18425, @0xKarl98), retaining 7702 authorizations while resolving a fee token (#18428, @stevencartavia), and ignoring
CHAINincast wallet newunless opted in (#18420, @stevencartavia).

Tests and developer output
forgenow minimizes stateless fuzz counterexamples—inputs found by randomized tests that demonstrate a failure (#18391, @stevencartavia). In invariant testing, which checks that a property continues to hold, a fix retains progress made while shrinking a failing case when the deadline is reached (#18414, @stevencartavia).forgekeeps live logs out of JSON output (#18419, @stevencartavia) and limits test discovery to project paths (#18424, @0xKarl98). The formatter ignores blank lines when inlining bodies (#18422, @stevencartavia).

Execution and internals
- EVM changes reduce per-opcode and per-call test overhead (#18412, @figtracer) and clear storage belonging to committed contract creations (#18359, @stevencartavia). Forked-state handling prefetches the state of simulated calls (#18247, @figtracer).
- A cheatcode fix retains writes made after reverted restores (#18174, @stevencartavia). Symbolic-execution code was refactored to remove unused solver and ABI code (#18429, @stevencartavia).
Source: github.com (originally published 2026-11-13 15:10 UTC+8)
