Please upgrade crate rusqlite to v0.37.
-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmlbdfEMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEh2EQP/2OEdJjx7lBVK1GPcxpS2zT+MWVTYiJWkX9feEKk
ihW1H/R6eTybXA6MEWiK8huCU2khPC9+jMPQ+oTJSo7L6xZW7NoAXcq8eQ9GjVCs
e+enPDBfU7ZTQd5HN9ghHj7+2zNnLkeHRlzITR0dFGu47zjih2XVsT0drYexVVxI
6apdQRBoeo0INtn3rhI2w1N3jzxoGDltvlidZJW5CFDxzrY/uPb/CouE9D3XR0kx
Y2cZ7nFBLqshVYtWmQ74NBVDvv0rKb4p6gX/y2uBCVI+JhLe9mqHzIvng5IV/CFV
oEA3w/GeaKhD1eJmxKZ3UyNjlNDWjFGwhN/68XRhSNUuZvBY9WyAK+tkC2tMer/v
DGZOFuywWYzhmMXvfAliqzpl+b+Z91VRO3ivzuhA5fsrdktdWF3jb0kDUESanGqi
1XUwSXmYLoh7uuC0mg2TRiQqYMft/a5FOpwR2YykqWTAAHiz/GBvZZ1ffqyEKPGa
MmyyH3ZquHbr8QhbTTwuxAHX3mLTInvtEYWrIQ1qZwZAlfXbyBrux0qVrehsK+3M
KUKau6ARJNvZn0/SxqbPBuDU71KnULsdeXoCi2J0RDTCo18odjmITIDi34UdLl/l
ly1cCTLQ/ddT0ulabHakD8FfCb9dVykVfqWC23+1EsV6d/Kb5cNYWfasVVQlsylw
/c+i
=Iwf6
-----END PGP SIGNATURE-----

Based on my preliminary analysis (see below) my feeling is we should go
straight for 0.38, I'll start preparing that soon if noone objects.

preliminary analysis.

libchewing - has no upper limit on the dependency upstream.
meli - uses 0.37 upstream, Debian is downpatching
rust-cargo - upstream git uses 0.38, upstream version in Debian uses
0.32. No code changes but an extra feature flag was added when updating
to 0.38.
rust-erbium-core - upstream uses 0.29
rust-hickory-server - upstreaqm uses 0.35
rust-parsec-service - upstream uses 0.29
rust-rustyline - upstream uses 0.37
rust-sequoia-cert-store - upstream allows up to 0.37
rust-sequoia-chameleon-gnupg - upstream allows up to 0.31
rust-sequoia-octopus-librnp - - upstream allows up to 0.31
rust-sequoia-sq - upstream allows up to 0.32
rust-tokio-rusqlite - upstream uses 0.37
settle - upstream uses 0.29

"Breaking changes" from upstream changelog.

0.38

  * Disable u64, usize ToSql/FromSql impl by default #1732
    <https://github.com/rusqlite/rusqlite/pull/1732>, ##1722
    <https://github.com/rusqlite/rusqlite/issues/1722> (breaking change)
  * Make statement cache optional #1682
    <https://github.com/rusqlite/rusqlite/pull/1682>, #1173
    <https://github.com/rusqlite/rusqlite/issues/1173> (breaking change)
  * Bump minimal SQLite version to 3.34.1 #1733
    <https://github.com/rusqlite/rusqlite/pull/1733>, #1731
    <https://github.com/rusqlite/rusqlite/issues/1731> (breaking change)
  * Check Connection is owned when registering Closure as hook #1764
    <https://github.com/rusqlite/rusqlite/pull/1764> (breaking change)

0.37

no breaking changes listed

0.36

no breaking changes listed

0.35

  * Breaking change: Check that Connection::execute has no tail #1679
    <https://github.com/rusqlite/rusqlite/pull/1679> / #397
    <https://github.com/rusqlite/rusqlite/issues/397>
  * Breaking change: Check for multiple statements in prepare #1680
    <https://github.com/rusqlite/rusqlite/pull/1680> / #1147
    <https://github.com/rusqlite/rusqlite/issues/1147>

no breaking changes were listed for versions 0.31 through 0.34

0.30

  * [breaking change] Update edition from 2018 to 2021 #1267
    <https://github.com/rusqlite/rusqlite/pull/1267>

Quoting Peter Michael Green (2026-02-01 17:50:42)

Regarding meli and settle, please go ahead - and no need to prepare a
patch (I'll take the chance and will cry out if I run into trouble).

Thanks,

 - Jonas

I've taken a preliminary look through the rdeps amd they seem quite spread out, but the most
important ones seem to have updated.

libchewing - dependency has no upper limit - testing needed.
meli - broken and not in testing
ripgrep-all - latest upstream uses 0.30, Debian package seems to upgrade to 0.32 and downgrade again?!
rust-cargo - upstream version in Debian uses 0.36, upstream git uses 0.39, no code changes when upgrading, but one cargo feature change https://github.com/rust-lang/cargo/commit/314367b398bff11893fd844d3f1f7665b65c35ec
rust-erbium-core - upstream allows versions 0.28 to 0.37 inclusive
rust-inquest - upstream allows versions 0.29 to 0.39 inclusive
rust-parsec-service - still uses 0.29 upstream
rust-sequoia-cert-store - upstream allows versions 0.29 to 0.39 inclusive
rust-sequoia-chameleon-gnupg - latest upstream release allows versions 0.29 to 0.31 inclusive, upstream git  allows versions 0.29 to 0.39 inclusive, upstream made no code changes when relaxing the dependency
rust-sequoia-octopus-librnp - latest upstream release allows versions 0.24 to 0.31 inclusive, upstream git is the same
rust-sequoia-sq - latest upstream release allows versions 0.24 to 0.32 inclusive, upstream git is the same
rust-taskchampion - latest upstream uses 0.37 but is semver breaking, upstream git uses 0.39, upstream made no code changes when updating but did make a change to enabled featureshttps://github.com/GothenburgBitFactory/taskchampion/commit/e35105e45a040113004a356046a24a467b23436b
rust-tokio-rusqlite - latest upstream uses 0.37, has a minor semver bump which we may as well take as part of this update
settle - still on 0.29 upstream

IMO we should try preparing an update to the latest version (0.39)
and only look at lower versions if that proves impractical.

Anyone else have any thoughts?