Skip to content

Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 #44769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
shmsr merged 3 commits into from
Jun 12, 2025
Merged

Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 #44769

shmsr merged 3 commits into from
Jun 12, 2025

Conversation

@shmsr
Copy link
Member

@shmsr shmsr commented Jun 12, 2025 •
edited
Loading

Proposed commit message

Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4. v1.14.0 is known to have a connection leak bug. Please read this for more details.

It was indirectly upgraded here: #41014 and 8.16.x and higher stacks are affected by the connection leak when using the mongodb module.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@shmsr shmsr requested a review from a team as a code owner June 12, 2025 06:30
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 12, 2025
@shmsr shmsr self-assigned this Jun 12, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jun 12, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@shmsr shmsr added the Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team label Jun 12, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 12, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 12, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@shmsr shmsr changed the title Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 Jun 12, 2025
@shmsr shmsr changed the title Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 Jun 12, 2025
@shmsr shmsr requested review from a team and mykola-elastic June 12, 2025 07:31
@shmsr shmsr added bug backport-active-all Automated backport with mergify to all the active branches labels Jun 12, 2025
mykola-elastic
mykola-elastic approved these changes Jun 12, 2025
View reviewed changes
Copy link
Contributor

@mykola-elastic mykola-elastic left a comment

Choose a reason for hiding this comment

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

LGTM! Let's see what the "checks" say

@shmsr shmsr added backport-8.17 Automated backport with mergify backport-8.x Automated backport to the 8.x branch with mergify backport-8.18 Automated backport to the 8.18 branch backport-9.0 Automated backport to the 9.0 branch and removed backport-8.x Automated backport to the 8.x branch with mergify backport-8.17 Automated backport with mergify backport-8.18 Automated backport to the 8.18 branch backport-9.0 Automated backport to the 9.0 branch labels Jun 12, 2025
@shmsr
Copy link
Member Author

shmsr commented Jun 12, 2025

@lalit-satapathy / @tommyers-elastic Can you please approve this PR?

@shmsr shmsr merged commit df335f3 into elastic:main Jun 12, 2025
203 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Jun 12, 2025

@Mergifyio backport 8.17 8.18 8.19 9.0

@mergify
Copy link
Contributor

mergify bot commented Jun 12, 2025 •
edited
Loading

backport 8.17 8.18 8.19 9.0

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 12, 2025
@shmsr @mergify
Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 (#4…
ad6a14e 
…4769)

(cherry picked from commit df335f3)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify bot mentioned this pull request Jun 12, 2025
Merged
6 tasks
mergify bot pushed a commit that referenced this pull request Jun 12, 2025
@shmsr @mergify
Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 (#4…
77fd7dd 
…4769)

(cherry picked from commit df335f3)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify bot mentioned this pull request Jun 12, 2025
Merged
6 tasks
mergify bot pushed a commit that referenced this pull request Jun 12, 2025
@shmsr @mergify
Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 (#4…
bec554a 
…4769)

(cherry picked from commit df335f3)
@mergify mergify bot mentioned this pull request Jun 12, 2025
Merged
6 tasks
mergify bot pushed a commit that referenced this pull request Jun 12, 2025
@shmsr @mergify
Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 (#4…
e09f412 
…4769)

(cherry picked from commit df335f3)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify bot mentioned this pull request Jun 12, 2025
Merged
6 tasks
shmsr pushed a commit that referenced this pull request Jun 13, 2025
@mergify
[8.17](backport #44769) Upgrade go.mongodb.org/mongo-driver from `v…
5f31d74 
…1.14.0` -> `v1.17.4` (#44776)
shmsr pushed a commit that referenced this pull request Jun 13, 2025
@mergify
[8.18](backport #44769) Upgrade go.mongodb.org/mongo-driver from `v…
304061a 
…1.14.0` -> `v1.17.4` (#44777)
shmsr pushed a commit that referenced this pull request Jun 13, 2025
@mergify
[9.0](backport #44769) Upgrade go.mongodb.org/mongo-driver from `v1…
a85fdc7 
….14.0` -> `v1.17.4` (#44779)
shmsr added a commit that referenced this pull request Jun 13, 2025
@mergify @shmsr
Upgrade go.mongodb.org/mongo-driver from v1.14.0 -> v1.17.4 (#4…
925e167 
…4769) (#44778)

(cherry picked from commit df335f3)

Co-authored-by: subham sarkar <subham.sarkar@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tommyers-elastic tommyers-elastic tommyers-elastic approved these changes

@mykola-elastic mykola-elastic mykola-elastic approved these changes

Assignees

@shmsr shmsr

Labels

backport-active-all Automated backport with mergify to all the active branches bug Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Upgrade mongodb driver from 1.14.0 to 1.17.4

4 participants

@shmsr @tommyers-elastic @mykola-elastic @ishleenk17