Skip to content

Update MongoDB.Driver PackageReference to 3.0.0#2580

Merged
stevejgordon merged 7 commits into
elastic:mainfrom
badge2033:badge2033-update-MongoDB.Driver
Aug 16, 2025
Merged

Update MongoDB.Driver PackageReference to 3.0.0#2580
stevejgordon merged 7 commits into
elastic:mainfrom
badge2033:badge2033-update-MongoDB.Driver

Conversation

@badge2033
Copy link
Copy Markdown
Contributor

update MongoDB.Driver PackageReference to 3.3
in this version package MongoDB.Driver.Core was merged with the main package and so was removed

remove MongoDB.Driver.Core package
update MongoDB.Driver package to version 3.3.0
remove reference to MongoDB.Driver.Core package and replace it with reference to MongoDB.Driver
@cla-checker-service
Copy link
Copy Markdown

cla-checker-service Bot commented Apr 1, 2025

💚 CLA has been signed

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 1, 2025

👋 @badge2033 Thanks a lot for your contribution!

It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it.

Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.

@badge2033
Copy link
Copy Markdown
Contributor Author

fixes issue #2504

@codewithmecoder
Copy link
Copy Markdown

Please help review and release on this merge on this as I am stack with the version conflict and cannot update MongoDB.Driver to version 3+.

Thank you.

@stevejgordon
Copy link
Copy Markdown
Contributor

We need to consider this one a bit more. The issue is, for consumers using older packages, this may cause conflicts and breaking changes, which we need to manually test and validate.

@badge2033
Copy link
Copy Markdown
Contributor Author

We need to consider this one a bit more. The issue is, for consumers using older packages, this may cause conflicts and breaking changes, which we need to manually test and validate.

i think this reasoning -while valid- is counter productive.
multiple projects are locked from a needed update for the mongo packages because of the desynchronised dependencies on the elastic packages.
But conservative project managers who are not keen on speedy updating, will stay on elastic old packages version, so they won't be affected either way.
please reconsider this update as very urgent.

Copy link
Copy Markdown
Contributor

@stevejgordon stevejgordon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@badge2033, we've discussed the options and agree that moving to the 3.x version is th best option to unblock users wanting the newer releases and DB support. We'll cover the breaking change in the release notes and docs. I've proposed one small change.

Comment thread Directory.Packages.props Outdated
@badge2033 badge2033 requested a review from stevejgordon August 16, 2025 13:37
@stevejgordon stevejgordon enabled auto-merge (squash) August 16, 2025 14:07
@stevejgordon
Copy link
Copy Markdown
Contributor

run docs-build

@stevejgordon stevejgordon merged commit 913b635 into elastic:main Aug 16, 2025
19 checks passed
@stevejgordon stevejgordon changed the title update MongoDB.Driver PackageReference to 3.3 Update MongoDB.Driver PackageReference to 3.0.0 Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants