Skip to content
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.

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

Bump mongodb from 3.3.3 to 3.5.3 #172

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Feb 13, 2020

Bumps mongodb from 3.3.3 to 3.5.3.

Release notes

Sourced from mongodb's releases.

v3.5.3

The MongoDB Node.js team is pleased to announce version 3.5.3 of the driver

Release Highlights

This patch release fixes one issue with command error handling during network errors, and one minor issue with multiple incoming wire messages not being properly processed.

Release Notes

Bug

  • [NODE-2435] - Unified topology does not transition server to Unknown on non-timeout operation error
  • [NODE-2437] - Multiple incoming message packets are not processed correctly

Improvement

  • [NODE-2438] - Add exhaust command support to transport layer
  • [NODE-2449] - Simplify server error handling in unified topology

v3.5.2

The MongoDB Node.js team is pleased to announce version 3.5.2 of the driver

Release Highlights

This patch release corrects a regression introduced in the 4.2 timeframe which would effectively disable retryable operations for connection to MongoDB 4.2+. Additionally, the server selection loop has been converted to a queue of callbacks to improve readability, as well as performance in certain scenarios.

Release Notes

Bug

  • [NODE-2408] - retryWrites seems not to work as expected in failover test

Improvement

  • [NODE-2398] - Use a queue for server selection
... (truncated)
Commits
  • d4e12db chore(release): 3.5.3
  • 5bf0df8 refactor: improve error handling in Server type
  • 21195ce test: ensure OP_MSG exhaust test is only run on standalones
  • fc1a775 refactor: errors before handshake should mark server unknown
  • 38ae86d chore(topology): remove commented out legacy code
  • 9ccf268 feat(connection): support exhaust behavior at the transport level
  • 8388443 fix(message-stream): support multiple inbound message packets
  • fa4b01b fix(server): non-timeout network errors transition to Unknown state
  • 3efa4c7 refactor(server): make common operation result handler
  • b740940 docs: provide basic migration updates for v3.5.xwq
  • Additional commits viewable in compare view

Dependabot compatibility score

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 dependabot-preview bot added the dependencies Pull requests that update a dependency file label Feb 13, 2020
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling fbc9239 on dependabot/npm_and_yarn/mongodb-3.5.3 into 9866d65 on master.

@dependabot-preview
Copy link
Contributor Author

Looks like mongodb is up-to-date now, so this is no longer needed.

@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/mongodb-3.5.3 branch February 23, 2020 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant