chore(deps): bump diesel-async from 0.7.4 to 0.9.0

[dependabot]

Bumps diesel-async from 0.7.4 to 0.9.0.

Release notes

Sourced from diesel-async's releases.

Diesel-Async 0.9.0

Changes

• Change all transaction related functions to accept an real async closure instead of the scoped boxed variant. This change requires adujsting all call sides of transaction based functions from conn.transaction(|conn| async move {/* your code */}.scoped_boxed()) to conn.transaction(async |conn| /* your code */)

Fixed

• Fixed an unsound access to padding values while deserializing Date/Time values in the mysql backend Thanks to @​paolobarbolini for finding this issue.

You can support the development of Diesel by:

• Contributing Code, Documentation or Guides. Checkout the planing for Diesel 2.4 for open tasks.
• Providing knowledge and help to maintain the MySQL/MariaDB backend. This is currently the only in-tree backend that is not used by any maintainers, so having someone around that actually uses this backend would be very helpful for the Diesel project.
• Answering questions in our discussion forum
• Reporting bugs in our issue tracker
• Helping triaging issues in our issue tracker
• Sponsoring the maintainers.

Full Changelog: diesel-rs/diesel_async@v0.8.0...v0.9.0

v0.8.0

What's Changed

• Added support for UpdateAndFetchResults for SyncConnectionWrapper, allowing to use save_changes
• Bumped supported deadpool version to 0.13
• Fixed a bug with postgres query pipelining that can cause panics
• Fixed a bug with the SyncConnectionWrapper that can cause panics if the future is dropped before completion

You can support the development of Diesel by:

• Contributing Code, Documentation or Guides. Checkout the planing for Diesel 2.4 for open tasks.
• Providing knowledge and help to maintain the MySQL/MariaDB backend. This is currently the only in-tree backend that is not used by any maintainers, so having someone around that actually uses this backend would be very helpful for the Diesel project.
• Answering questions in our discussion forum
• Reporting bugs in our issue tracker
• Helping triaging issues in our issue tracker
• Sponsoring the maintainers.

New Contributors

• @​epompeii made their first contribution in weiznich/diesel_async#272
• @​Hao2203 made their first contribution in weiznich/diesel_async#273
• @​766974616c79 made their first contribution in weiznich/diesel_async#275
• @​TheNeikos made their first contribution in weiznich/diesel_async#279
• @​dav-wolff made their first contribution in weiznich/diesel_async#283

Full Changelog: diesel-rs/diesel_async@v0.7.4...v0.8.0

Changelog

Sourced from diesel-async's changelog.

[0.9.0] - 2026-04-30

• Change all transaction related functions to accept an real async closure instead of the scoped boxed variant. This change requires adujsting all call sides of transaction based functions from conn.transaction(|conn| async move {/* your code */}.scoped_boxed()) to conn.transaction(async |conn| /* your code */)
• Fixed an unsound access to padding values while deserializing Date/Time values in the mysql backend Thanks to Paolo Barbolini for finding this issue.

[0.8.0] - 2026-03-20

• Added support for UpdateAndFetchResults for SyncConnectionWrapper, allowing to use save_changes
• Bumped supported deadpool version to 0.13
• Fixed a bug with postgres query pipelining that can cause panics
• Fixed a bug with the SyncConnectionWrapper that can cause panics if the future is dropped before completion

Commits

• 18f2c86 Merge pull request #285 from diesel-rs/fix/padding_access
• acc90e9 Prepare a 0.9 release
• ba3ed66 Merge pull request #284 from diesel-rs/async_closures
• 4e2fc54 Use real async closures for transactions
• 237ac09 Prepare 0.8.0
• 67e3e3f Merge pull request #282 from dav-wolff/fix-sync-connection-wrapper-panic
• 03caa1e Replace timeout based tests with more robust channel usage
• 7df84d8 Merge pull request #283 from dav-wolff/remove-unsafe-pin-projection
• b426870 Use pin_project_lite instead of manually pin-projecting
• 7dacba2 Remove pin-project dependency
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.