chore(deps): update rust crate mongodb to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
mongodb (source)	workspace.dependencies	major	2.8.0 -> 3.0.0

---

Release Notes

mongodb/mongo-rust-driver (mongodb)

v3.1.0

Compare Source

The MongoDB Rust driver team is pleased to announce the v3.1.0 release of the mongodb crate, now available for download from crates.io.

This release provides compatibility with MongoDB 8.0, including support for a number of new in-use encryption features.

Full Release Notes

Features

• RUST-1813 Support for more than one KMS provider per type (#​1141)
• RUST-1843 Support for QE range protocol V2 (#​1132)
• RUST-1845 Support search index type field (#​1147)
• RUST-1926 Support range indexes as GA (#​1184)

Improvements

• RUST-1994 Implement happy eyeballs for TCP connection (#​1183)
• RUST-1791 Publish an event changing topology state to unknown before closing (#​1160)
• RUST-1980 Bump dependencies (#​1142) (thanks @​attila-lin!)

Tasks

• RUST-1821 Increase minimum compatible MongoDB server version to 4.0 (#​1151)
• RUST-1981 Increase maximum compatible MongoDB server version to 8.0 (#​1175)

v3.0.1

Compare Source

The MongoDB Rust driver team is pleased to announce the v3.0.1 release of the mongodb crate, now available for download from crates.io.

This release fixes two bugs:

• Aggregations with both explicit sessions and custom types wouldn't compile, and
• Collection::watch didn't use the Collection's type parameter

Full Release Notes

Bugfixes

• RUST-1986 Use Collection type parameter for change streams (#​1162)
• RUST-1982 Fix aggregate with_type with explicit session (#​1155)

v3.0.0

Compare Source

The MongoDB Rust driver team is pleased to announce the v3.0.0 release of the mongodb crate, now available for download from crates.io.

Highlighted Changes

Breaking Changes

3.0 introduces a wide variety of improvements that required backwards-incompatible API changes; in most cases these changes should require only minor updates in application code.

Most notably:

• Fluent API: Async methods that accepted options have been updated to allow the individual options to be given directly in line with the call to reduce required boilerplate.
• Events: 3.0 introduces the EventHandler type, which can be constructed from a callback, async callback, or an async channel sender.
• Async Runtime: 3.0 only supports tokio; support for async-std has been discontinued.

For detailed information on breaking changes and examples of migrating from 2.x to 3.0, please see the migration guide.

Bulk Write

The Rust driver now implements the new Bulk Write specification, which supports performing mixed write operations against multiple namespaces in a minimized number of round-trips to the server. This feature is only available for early testing using MongoDB 8.0 release candidate binaries. This feature is not recommended for use in production until the stable release of MongoDB 8.0.

OIDC Authentication

The Rust driver can now authenticate using an OpenID Connect access token, including support for both the machine and human authentication flows, and automatic token acquisition for Azure and GCP.

Included Changes

Below are a selected list of other changes with user impact; for a full list of changes see this GitHub query.

Breaking Changes

• RUST-1810 Clean up concern helpers (#​1011)
• RUST-1603 Support the authorized_collections option (#​1033)
• RUST-1876 Require T: Send + Sync for Collection (#​1043)
• RUST-1306 Move Compression enum behind compression feature flags (#​1055)
• RUST-1563 Make ReadPreferenceOptions optional (#​1059)
• RUST-1208 Future-proof features (#​1062)
• RUST-1764 Drop human_readable options in favor of HumanReadable (#​1064)
• RUST-1695 Use consistent defaults for TypedBuilder (#​1072)
• RUST-1364 Collapse comment and comment_bson (#​1070)

New Features

• RUST-1652 Add a find_one method to GridFsBucket (#​1015)
• RUST-1856 expose Database::client (#​1035) (thanks dgrijalva!)
• RUST-1830 Support KMIP delegated protocol (#​1115)

Improvements

• chore: bump socket2 to 0.5 (#​1020) (thanks attila-lin!)
• chore: move lazy_static to once_cell (#​1022) (thanks attila-lin!)
• RUST-1631 Always use polling monitoring when running in a FaaS environment (#​1030)

Bugfixes

• RUST-1881 Check integer conversions (#​1045)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `mongodb`.
    ... required by package `sos24-infrastructure v0.1.0 (/tmp/renovate/repos/github/sohosai/sos24-server/crates/sos24-infrastructure)`
    ... which satisfies path dependency `sos24-infrastructure` (locked to 0.1.0) of package `sos24-presentation v0.1.0 (/tmp/renovate/repos/github/sohosai/sos24-server/crates/sos24-presentation)`
versions that meet the requirements `^3.0.0` are: 3.1.0, 3.0.1, 3.0.0

the package `sos24-infrastructure` depends on `mongodb`, with features: `bson-chrono-0_4` but `mongodb` does not have these features.


failed to select a version for `mongodb` which could resolve this conflict