I’ve released a new beta version of rusqlite_migration today and I’ve
renamed the `async-tokio-rusqlite` feature that you use to
`alpha-async-tokio-rusqlite`. I suggest updating dependencies as done in
this PR. By the way, if you would like to share feedback on the async
APIs, feel free to use this conversation:
https://github.com/cljoly/rusqlite_migration/discussions/127
Reading the release notes from [tokio-rusqlite][1], the main breaking
change is to the method `Connection::call`:
> - **breaking:** `Connection::call` now takes `tokio_rusqlite::Result` instead
> of `rusqlite::Result`.
My understanding is that we can either deal with a `Result<Result<…>>`
or call `Connection::call_unwrap`, which could panic if the connection
is closed. I’ve opted for using only `Connection::call` and,
effectively, flattening the `Result<Result<…>>`, to limit the potential
for panics.
[1]: https://github.com/programatik29/tokio-rusqlite/blob/master/CHANGELOG.md#050-25-nov-2023
* feat(tabby-webserver): when user is registered with invitation code, delete invitation when user is created
* update cmts
* [autofix.ci] apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* extract schema::User as format for MeQuery
* refactor: restructure JWTPayload
* feat: update frontend to adapt JWT token format change
* delete generated files
Clément Joly