chore(deps): update module go.mongodb.org/mongo-driver to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.mongodb.org/mongo-driver	v1.17.3 -> v2.2.0

---

Release Notes

mongodb/mongo-go-driver (go.mongodb.org/mongo-driver)

v2.2.0: MongoDB Go Driver 2.2.0

Compare Source

The MongoDB Go Driver team is pleased to release version 2.2.0 of the official MongoDB Go Driver.

Release Notes

This release includes support for a global omitempty setting to omit empty values when encoding BSON, instead of requiring tagging on individual struct fields. We have implemented support for errors.Is and errors.As in all stable public APIs for improved error management. Also included is support to configure the lifetime of the Data Encryption Key (DEK) cache as well as Kubernetes Support for OIDC.

Additionally MongoDB Server Version 3.6 has been marked as end-of-life (EOL) and is no longer supported by the driver. Users are advised to upgrade to a supported version.

---

For a full list of tickets included in this release, please see the links below:

• New Features
• Improvements
• Bugs
• Tasks

Full Changelog: v2.1.0...v2.2.0

Note: The Go Driver team has implemented a workflow action to automatically merge up PRs between v1 and master. This has resulted in an over-extended changelog for this version, including v1 commits for PRs that have already been cherry-picked to master. Please see the associated tickets for commits directly associated with this release.

Documentation for the MongoDB Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the MongoDB Go Driver is greatly appreciated!

v2.1.0: MongoDB Go Driver 2.1.0

Compare Source

The MongoDB Go Driver Team is pleased to release version 2.1.0 of the official MongoDB Go Driver.

Release Notes

This release adds support for the new bulk write API added in MongoDB 8.0 and the new BSON vector datatype used in Atlas Vector Search.

Additionally, support for MongoDB 3.6 and below was deprecated in v2.0.0 and will be dropped in the next minor version release (v2.2.0).

New BulkWrite API

The new Client.BulkWrite method can perform many insert, update, and delete operations on multiple databases and collections in one request. In contrast, the existing Collection.BulkWrite method can only modify a single collection.

BSON Vector Datatype

The new bson.Vector type makes inserting and querying vector data using Atlas Vector Search easier and more efficient.

---

For a full list of tickets included in this release, please see the links below:

• New Features
• Improvements
• Bugs
• Tasks

Full Changelog: v2.0.1...v2.1.0

Documentation for the MongoDB Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the MongoDB Go Driver is greatly appreciated!

v2.0.1: MongoDB Go Driver 2.0.1

Compare Source

The MongoDB Go Driver team is pleased to release version 2.0.1 of the official MongoDB Go Driver.

Release Notes

This release includes various bug fixes and improvements:

• Allows SRV hostnames with only a domain name and TLD (e.g. "service-name.tld").
• Detects joined errors correctly in IsNetworkError and WithTransaction.
• Fixes a memory buffer reuse bug in MarshalValue that can cause marshaled bytes to become corrupted.
• No longer returns nil from MergeClientOptions when only one nil argument is passed.
• Skips calling UnmarshalBSONValue only if the associated BSON field value is null and the Go value is a pointer.

---

For a full list of tickets included in this release, please see the links below:

• Bugs
• Tasks

Full Changelog: v2.0.0...v2.0.1

Documentation for the MongoDB Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the MongoDB Go Driver is greatly appreciated!

v2.0.0: MongoDB Go Driver 2.0.0

Compare Source

The MongoDB Go Driver Team is pleased to release version 2.0.0 of the official MongoDB Go driver.

Release Notes

This release includes a host of new features and several breaking changes. Below, we provide an overview of the key highlights, changes, and guidance for migrating from version 1.x to 2.0. See the MongoDB docs for a complete list of breaking changes and additional information on what's new.

This release includes several breaking changes that users must account for when upgrading, including:

• Options Package: The approach to managing options has been restructured to use a builder pattern, changing how options are constructed and applied. This alteration allows for more flexible and dynamic option configurations, but may require changes to existing code that directly manipulates options objects.
• Mongo Package: The Client.Connect() method has been removed, favoring mongo.Connect() to streamline connection handling.
• Event Package: References to the description package have been transitioned to event.ServerDescription and event.TopologyDescription, impacting how server and topology details are accessed.
• BSON Package Consolidation: All previously separate BSON-related packages, including bsoncodec, bsonoptions, bsonrw, and mgocompat, have been merged into the single bson package. Many functionalities from these packages have been reorganized or renamed. For instance, bson.NewRegistryBuilder has been replaced with new APIs tailored for registry configuration, and interfaces like ValueReader and ValueWriter are now part of the consolidated bson package. This consolidation simplifies the package structure but requires updates to import paths and related logic.

To ease the transition to 2.0, a comprehensive migration guide has been provided. This guide includes detailed instructions to navigate the changes, including the updated options pattern, altered imports, and revised method signatures.

Additionally, this release deprecates support for MongoDB server versions below 3.6. Support for MongoDB 3.6 will be dropped in a future update.

New features will no longer be added to the 1.x versions. However, critical bug fixes and CVE resolutions will continue to be back-ported to 1.x versions for one year until January 15, 2026. After that date, support for 1.x versions will be discontinued.

We express our gratitude to our contributors and the community for all the support in developing this release.

---

For a full list of tickets included in this release, please see the links below:

• Projects
• New Features
• Improvements
• Bugs
• Tasks

Full Changelog: v1.17.1...v2.0.0

Documentation for the Go driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go driver is greatly appreciated!

---

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: go.sum

Command failed: go mod tidy
go: downloading go.mongodb.org/mongo-driver/v2 v2.2.0
go: finding module for package go.mongodb.org/mongo-driver/v2/bson/primitive
go: github.com/DoodleScheduling/growthbook-controller/internal/growthbook tested by
	github.com/DoodleScheduling/growthbook-controller/internal/growthbook.test imports
	go.mongodb.org/mongo-driver/v2/bson/primitive: module go.mongodb.org/mongo-driver/v2@latest found (v2.2.0), but does not contain package go.mongodb.org/mongo-driver/v2/bson/primitive

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.