Diesel 2.0.0
What happened next
Four years on, Diesel is still on 2.x. 2.3.0 on 12 September 2025 is the newest minor, and its latest patch is 2.3.14.
Latest stable Diesel: 2.3.14, released (release notes). 30 stable releases since 15 Mar 2024.
Which database each release's notes name, 30 releases since January 2024. Right of the line: MySQL in 13 of 14.
Diesel 2.3.14 went up on crates.io on 7 October 2026. It fixes a failed top-level COMMIT on SQLite that left the transaction open, and stops the embed_migrations macro from breaking reproducible builds.
The 2.3.0 announcement in September 2025 asked for help with the MySQL and MariaDB backend, the only in-tree backend that no maintainer uses. 13 of the 14 patch releases since then name MySQL or MariaDB in their notes, and the 14th has no notes at all. In the 13 releases of 2.2, two did. The backend nobody on the team runs is the one taking the most fixes.
As of 24 October 2026.
2.3.14Add support for sqlite-wasm-rs 0.62.3.13Fixed interaction between then_order_by and distinct_on to reject otherwise broken SQL queries2.3.12Fixed FromSql/ToSql for chrono::NaiveTime on MySQL dropping the fractional-seconds component of TIME values, so a TIME(N) column now round-trips its microseconds like DATETIME / TIMESTAMP already did.2.3.11Fixed several potential panics in PostgreSQL (de)serialization code2.3.10Fixed a wrong value of a internal MYSQL flag2.3.9Removed a dbg! statement from the Mysql backend that caused unwanted output
Four years on, Diesel is still on 2.x. 2.3.0 on 12 September 2025 is the newest minor, and its latest patch is 2.3.14.
2.1 got its last patch, 2.1.6, on 19 April 2024, six weeks before 2.2.0 replaced it.
2.2 ran to 2.2.12 in July 2025. The 2.3 announcement counted more than 1142 commits from 95 people over 16 months, and added window functions and SQLite in the browser through WASM.