sqlx-sqlite requires libsqlite3-sys >=0.30.1, <0.38.0, on 0.9.0 and on main. That caps the bundled SQLite at 3.51.3 (libsqlite3-sys 0.37.0). Current is libsqlite3-sys 0.38.2, which bundles SQLite 3.53.2.
libsqlite3-sys 0.38.0 was published 2026-05-26 with rusqlite v0.40.0, five days after sqlx 0.9.0 released, so the bound was accurate when it was written.
It can't be worked around downstream. libsqlite3-sys sets links = "sqlite3", so cargo refuses two versions in one graph, and a direct dependency on 0.38 is a resolution error rather than an override. That leaves vendoring the crate or patching sqlx-sqlite.
Not urgent for correctness, since 3.51.3 already has the WAL-Reset fix, but anyone tracking SQLite releases is stuck two minor versions back.
Same change as #4161.
sqlx-sqliterequireslibsqlite3-sys >=0.30.1, <0.38.0, on 0.9.0 and on main. That caps the bundled SQLite at 3.51.3 (libsqlite3-sys 0.37.0). Current is libsqlite3-sys 0.38.2, which bundles SQLite 3.53.2.libsqlite3-sys 0.38.0 was published 2026-05-26 with rusqlite v0.40.0, five days after sqlx 0.9.0 released, so the bound was accurate when it was written.
It can't be worked around downstream.
libsqlite3-syssetslinks = "sqlite3", so cargo refuses two versions in one graph, and a direct dependency on 0.38 is a resolution error rather than an override. That leaves vendoring the crate or patchingsqlx-sqlite.Not urgent for correctness, since 3.51.3 already has the WAL-Reset fix, but anyone tracking SQLite releases is stuck two minor versions back.
Same change as #4161.