Bump mongo from 2.8.0 to 2.18.1

[dependabot[bot]]

Bumps mongo from 2.8.0 to 2.18.1.

Release notes

Sourced from mongo's releases.

2.18.1

This patch release in the 2.18 series adds the following new feature:

• RUBY-2886 FLE 1.0 Shared Library support

The following issues have also been addressed:

• RUBY-3073 Upgrade libmongocrypt dependency to 1.5.2
• RUBY-3077 Driver fails to load latest version of libmongocrypt
• RUBY-3025 getMore with a batchSize of 0 being sent if a limit of 0 is set
• RUBY-3044 Large bulk_write fails inside transactions
• RUBY-3054 Some find options are not sent to server

2.18.0

This feature release of the Ruby driver supports MongoDB version 6.0. It includes the following new features:

• Added support for queryable encryption.
• Added support for Azure Key Vault, Google Cloud Key Management, and any KMIP compliant Key Management System to be used as master key storage for client side encryption.
• It is now possible to provide the path to a schema map file instead of the entire schema map as an object.
• The driver now implements the feature flag mechanism for incompatible changes and bug fixes. Changes gated behind feature flags for 2.18 are passing view filter and options to aggregate and validation of correct usage of update vs replace methods, as described below.
• Added the validate_update_replace feature flag which validates the parameters to update and replace operations. If this flag is turned on, an error will be raised on an invalid update or replacement document.
• Added the broken_view_options feature flag which allows the view options to be correctly propagated to the aggregate, count, count_documents, distinct, and estimated_document_count mehods. When this flag is switched on, the view options will be ignored in those methods.
• The driver now permits inserting documents with dollar-prefixed and dotted keys.
• CRUD methods, methods for listing databases, collection, and indexes management methods now support a new option :comment. This option enables users to specify an arbitrary comment to help trace the operation through the database profiler, currentOp and logs.
• The estimated_document_count method is now using the count server command instead of $collStats` aggregation pipeline stage, to support operation on views. Applications using the Stable API should upgrade to server versions 5.0.8 (if using MongoDB 5.0) or 5.3.2 (if using MongoDB 5.1/5.2/5.3) or newer to use the count command when API strict is enabled, or avoid setting api_strict: true when constructing Mongo::Client instances with server versions 5.0.0-5.0.7 and 5.1.0-5.3.1.
• The DBRef class has been moved to bson-ruby. For backwards compatibility, BSON::DBRef is aliased as Mongo::DBRef. The BSON::DBRef class derives from BSON::Document, unlike the legacy Mongo::DBRef which derived from Object. BSON::DBRef retains all attributes passed into its constructor, unlike Mongo::DBRef which only allowed $ref, $id, and $db. BSON::DBRef also reorders the fields if necessary to place $ref, $id, and $db first, in that order, as required by the MongoDB server.
• BulkWrite::Result class now has the acknowledged? attribute.
• Providing an empty array of operations to the bulk write is now an error.
• BSON serialization performance has been improved.
• ActiveJob middleware was added to the query cache.
• :authorized_collections options is recognized when listing collections.
• :wildcard_projection option was added to the allowed index specification.
• Added :srv_max_hosts/srvMaxHosts Ruby and URI options to limit how many mongos routers the driver will establish connections to.
• Custom SRV service names are now supported with the :srv_service_name Ruby option and the srvServiceName URI option.
• When 0 is given as the max connection pool size, it is now interpreted to mean no limit.
• The default maximum connection pool size has been increased to 20 from 5.

The following minor improvements were made:

• RUBY-2736 Add server connectionId to command monitoring events

The following issues were addressed:

• RUBY-2972 Calling find_one_and_* methods with write_concern 0 causes an error
• RUBY-2923 Slow spawn of mongocryptd
• RUBY-2961 Zero & negative limits not emulated correctly by QueryCache
• RUBY-1869 watch methods unaffected by :max_await_time_ms
• RUBY-2869 ruby 3.1.0: finalizer can't synchronize using mutexes
• RUBY-2990 Terminate push monitor when it fails

... (truncated)

Changelog

Sourced from mongo's changelog.

.. _release-notes:

---

Release Notes

---

.. default-domain:: mongodb

This page documents significant changes in driver releases.

It is not an exhaustive list of changes and generally does not enumerate bug fixes; please consult the releases page on GitHub <https://github.com/mongodb/mongo-ruby-driver/releases>_ for a more comprehensive list of changes in each version of the driver and the releases page in Jira <https://jira.mongodb.org/projects/RUBY?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released>_ for the complete list of changes, including those internal to the driver and its test suite.

.. _release-notes-2.18:

2.18

This release of the Ruby driver supports MongoDB version 5.2 and 6.0.

This release includes the following new features:

• Added support for queryable encryption <https://www.mongodb.com/docs/upcoming/core/queryable-encryption/queryable-encryption/>_.
• Added support for Azure Key Vault, Google Cloud Key Management, and any KMIP compliant Key Management System to be used as master key storage for client side encryption.
• It is now possible to provide the :ref:path to a schema map file <schema-map-path> instead of the entire schema map as an object.
• The driver now implements the :ref:feature flag <feature-flags> mechanism for incompatible changes and bug fixes. Changes gated behind feature flags for 2.18 are passing view filter and options to aggregate and validation of correct usage of update vs replace methods, as described below.
• Added the validate_update_replace feature flag which validates the parameters to update and replace operations. If this flag is turned on, an error will be raised on an invalid update or replacement document.
• Added the broken_view_options feature flag which allows the view options to be correctly propagated to the aggregate, count, count_documents, distinct, and estimated_document_count mehods. When this flag is switched on, the view options will be ignored in those methods.
• The driver now permits :ref:inserting documents with dollar-prefixed and dotted keys <dots-dollars-in-field-names>.
• CRUD methods, methods for listing databases, collection, and indexes management methods now support a new option :comment. This option enables users to

... (truncated)

Commits

• 9e87516 Release 2.18.1
• a174dca RUBY-3057 Update FLE2 docs (#2570)
• fab5ce1 RUBY-3073 RUBY-3077 Fix LMC version check (#2571)
• 6b1c149 RUBY-3063 sync transactions spec tests (#2569)
• bb2e434 RUBY-3053 update Spec test "change stream resumes after StaleShardVersion" fo...
• b992c29 RUBY-3050 Improve reliability of SDAM heartbeat error spec tests. (#2567)
• 022160e RUBY-3025 Fix cursor batchSize if limit is zero (#2566)
• 0029406 RUBY-2886 Add FLE shared lib support (#2564)
• 4a74ac7 RUBY-3061 Script to retrieve Atlas certificates for test suite (#2565)
• b50d12e RUBY-3044 Fix bulk_write in transaction (#2563)
• 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.