v111
Date: 2026-05-22
v111 is a maintenance release that extends DBErrorMarker so callers can distinguish fatal database errors from recoverable BAL validation failures (#3704). The change adds is_fatal(&self) -> bool to the DBErrorMarker trait with a default of true, preserving existing fail-stop behavior for every current implementor. EvmDatabaseError overrides the default so the Database(_) variant is fatal and the Bal(_) variant is non-fatal — letting callers distinguish a real underlying database failure from a BAL validation issue that may be retried or surfaced differently.
Version bumps
revm-database-interface: 12.0.0 → 12.1.0 (✓ API compatible changes)revm-context-interface: 19.0.1 → 19.0.2 (✓ dependency bump)revm-context: 18.0.1 → 18.0.2 (✓ dependency bump)revm-database: 15.0.0 → 15.0.1 (✓ dependency bump)revm-interpreter: 37.0.1 → 37.0.2 (✓ dependency bump)revm-precompile: 36.0.1 → 36.0.2 (✓ dependency bump)revm-handler: 20.0.1 → 20.0.2 (✓ dependency bump)revm-inspector: 21.0.1 → 21.0.2 (✓ dependency bump)revm-statetest-types: 19.0.1 → 19.0.2 (✓ dependency bump)revm: 40.0.1 → 40.0.2 (✓ dependency bump)revme: 17.0.1 → 17.0.2 (✓ dependency bump)
Commits
- feat(database): add
is_fataltoDBErrorMarkerby @rakita in #3704 - chore: release by @github-actions[bot] in #3705
- chore: v111 release prep by @rakita in #3706
Full Changelog: v110...v111