Update mongoid requirement from ~> 6.0 to ~> 7.2

[dependabot-preview]

Updates the requirements on mongoid to permit the latest version.

Release notes

Sourced from mongoid's releases.

7.2.2

This patch release in the 7.2 series repairs a Rails 6.1 incompatibility in the Mongoid config generator and fixes several user-reported problems. The following issues have been resolved:

• MONGOID-5042 rails g mongoid:config is not working on Rails 6.1
• MONGOID-5063 Support numeric path components as hash keys when embedded matching
• MONGOID-5069 Support numeric path components resolving to hash keys under arrays when embedded matching
• MONGOID-5059 set nilifies attributes excluded via only
• MONGOID-5068 ElemMatch matcher operates on pre-stringified keys in condition verification path against impossible values
• MONGOID-5076 reload fails to find document when the document's sharded field has been updated

7.2.1

This patch release in the 7.2 series adds compatibility with Rails 6.1 and fixes the following issues:

• MONGOID-5033 Cannot use any_of with multiple conditions when using symbol operators on Time fields and passing Date instances
• MONGOID-5035 Query embedded documents by date field with $gt/gte/lt/lte does not find existing documents

7.2.0

This feature release of Mongoid includes the following principal changes:

• Embedded matchers have been largely rewritten. In several cases the behavior of Mongoid matchers was changed to match MongoDB server. Please see the upgrading guide section for detailed changes.
• Model#count is now implemented using the aggregation pipeline $count stage. Model#estimated_count method was added to provide the estimated count that Model#count used to provide. This change should be transparent to most applications but may increase runtime for applications that call #count, especially with complex conditions (with the benefit being of #count producing accurate results). See this upgrading guide section for further details.
• Discriminator key and value can now be overridden for models using inheritance.
• Shard key is now used when reloading models for improved performance in sharded deployments.
• The query cache was moved to the driver. Mongoid 7.2 will transparently use the query cache implementation in driver versions 2.14 and higher, with a fallback on the legacy query cache implementation that will continue to be provided for when Mongoid is used with older driver versions. The driver's query cache implementation provides new features such as caching the aggregation pipelines and more fine grained cache expiration. Both the driver's query cache implementation and Mongoid's legacy query cache implementation also contain fixes to known issues like inability to cache results when they are returned in multiple batches from the server.

The following additional improvements were made:

• MONGOID-4913 StringifiedSymbol field to expose strings as symbols in Ruby
• MONGOID-4914 Unmask Enumerable#find on one to many associations
• MONGOID-4522 Make #any? not retrieve entire result set, like #exists?
• MONGOID-4703 Add geo_spatial as an alias for geo_spacial

The following bugs have been fixed:

• MONGOID-4977 Use new send_initial_query signature in Mongoid QueryCache
• MONGOID-4890 Destroying model instances with dependent associations in transactions raises OperationFailure due to use of (deprecated) count
• MONGOID-4947 #any? method with block given does not behave as per Enumerable
• MONGOID-4980 Atomic push incorrectly determines whether there is a conflict
• MONGOID-5013 Re-associating identical object destroys itself for dependent: :destroy
• MONGOID-5002 parent.child = Child.new raises TypeError when there's no inverse relation for belongs_to with has_one parent

Support for Ruby MRI versions 2.3 and 2.4 has been deprecated as of this release. See this ticket for more details. We intend to stop supporting these Ruby versions as of Mongoid 7.3.

Please read the upgrading guide for the detailed list of changes, major new features and upgrading guidance.

7.2.0.rc1

This is a preview of the next feature release of Mongoid.

Mongoid 7.2 includes the following principal changes:

• Embedded matchers have been largely rewritten. In several cases the behavior of Mongoid matchers was changed to match MongoDB server. Please see the upgrading guide section for detailed changes.
• Model#count is now implemented using the aggregation pipeline $count stage. Model#estimated_count method was added to provide the estimated count that Model#count used to provide. This change should be transparent to most applications but may increase runtime for applications that call #count, especially with complex conditions (with the benefit being of #count producing accurate results). See this upgrading guide section for further details.

... (truncated)

Commits

• 4fce489 Release 7.2.2
• 64d4518 Fix MONGOID-5076 reload fails to find document when the document's sharded fi...
• b68a8ec Update shared refs
• 04accba MONGOID-5069 Support numeric path components resolving to hash keys under arr...
• 1183d33 Fix MONGOID-5059 set nilifies attributes excluded via only (#4978)
• 14e9704 Fix MONGOID-5068 ElemMatch matcher operates on pre-stringified keys in condit...
• 4fcbd1f MONGOID-5063 Support numeric path components when traversing hashes with dot ...
• 1ec1820 Fix MONGOID-5042 rails g mongoid:config is not working on Rails 6.1 (#4960)
• 77ec4cd MONGOID-5047 Take Rails versions from Evergreen configuration in app tests (#...
• b37fed6 Move virtualenv & mtools-legacy installation into Docker base image when poss...
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #119.