Skip to content

fix(deps): bump rusqlite 0.32 -> 0.41 for RUSTSEC-2026-0459 - #31

Merged
tinhtute merged 1 commit into
masterfrom
quaqua/sude-sqlitebump
Nov 12, 2026
Merged

tinhtute merged 1 commit into
masterfrom
quaqua/sude-sqlitebump

Conversation

@tinhtute

Copy link
Copy Markdown
Owner

Outcome: COMPLETE
Snapshot: see git log -1 on quaqua/sude-sqlitebump, worktree ~/Lab/.wt/sude-sqlitebump (not pushed)
Scope: Cargo.toml (workspace rusqlite "0.32" -> "0.41", features=["bundled"] kept), Cargo.lock. No source edits needed.
Verification: before: cargo tree -i libsqlite3-sys -> 0.30.1 <- rusqlite 0.32.1; cargo audit -> "1 vulnerability found" (RUSTSEC-2026-0459).
after: libsqlite3-sys 0.39.1 <- rusqlite 0.41.1; cargo audit exit 0, no vulnerabilities.
cargo fmt --all -- --check ok; clippy -D warnings clean; cargo test --workspace all ok (395 lib + eval_suite 6 + others, 0 failed);
make smoke -> "smoke: OK"; git diff --check ok.
Skipped: bench_100k perf run, release build.
Unknown / risk: 0.41.0 is the lowest release with libsqlite3-sys ^0.39 (0.40.x -> 0.38). Used "0.41" (resolved 0.41.1). Cargo.lock also moved transitive crates (hashlink, thiserror 2, serde patch, etc.) as rusqlite's deps require. Bundled SQLite version changed; tests/smoke show no FTS behavior change, existing on-disk indexes are disposable (reindex).
Ownership: released

from therealTINHTUTE with love ❤️❤️❤️

libsqlite3-sys 0.30.1 -> 0.39.1 (bundled SQLite CVE-2026-119375).

🥷 - from therealTINHTUTE with love
@tinhtute
tinhtute merged commit 4c1b29f into master Nov 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant