Release notes
*Sourced from [mongodb's releases](https://github.com/mongodb/node-mongodb-native/releases).*
> ## v3.3.5
> The MongoDB Node.js team is pleased to announce version 3.3.5 of the driver
>
> ## Release Highlights
>
> ### unified topology
> This patch release includes additional fixes for the regression in the unified topology discovered in v3.3.2, expanding our testing infrastructure to include a simulated workload during failover testing. There was a bug when connecting to single-node replicasets which could result in a stack overflow which was corrected. Additionally, events and options which are incompatible with the unified topology will now emit a warning message.
>
> ### mongodb+srv
> The release also includes a fix submitted by [@mpilar](https://github.com/mpilar), who found an inconsistency in our implementation of the "Initial Seedlist Discovery" specification. An `authSource` specified in the options passed to `MongoClient` would be overridden by an `authSource` provided in the TXT record checked during initial seedlist discovery over SRV. Thank you very much Miguel!
>
> ### bulkWrite
> `BulkWriteError` is now exported at the top level of the module so that users can catch them easily. Additionally, a fix was made to ensure that the index of operations passed into an `unordered` bulk operation were preserved when reporting possible errors in the future.
>
> ## Release Notes
>
Bug
>
>
>
[NODE-1747] - Replica set causes MongoNetworkError due to not connecting with fully qualified domain name
>
>
[NODE-2089] - Only apply TransientTransactionError label within a transaction
>
>
[NODE-2143] - getaddrinfo ENOTFOUND error on Windows 10 due to failed fallback to ipv4 after ipv6 lookup fails
>
>
[NODE-2308] - Bulk write error returns incorrect index in WriteError for unordered writes
>
[NODE-2335] - Node Driver does not follow Initial DNS Seedlist Discovery spec
>
>
[NODE-2342] - Enabling useUnifiedTopology results in stack overflow when connecting to uninitialized replica set
>
>
>
>
Improvement
>
>
>
[NODE-2348] - Document and notify on deprecated events and options for unified topology
>
>
[NODE-2306] - Driver module does not export `BulkWriteError`
>
>
>
>
> ## v3.3.4
> The MongoDB Node.js team is pleased to announce version 3.3.4 of the driver
>
> ## Release Highlights
> This release primary consists of improvements to the "unified topology". In particular, a regression with interaction between the connection pool and topology could result in servers which "go away" (due to network error, for example) would not return, resulting in a `MongoTimeoutError`.
>
> ... (truncated)
Commits
- [`6930e12`](https://github.com/mongodb/node-mongodb-native/commit/6930e1265c1dae7a5c219b993be1f90b28a40851) chore(release): 3.3.5
- [`b0f83b8`](https://github.com/mongodb/node-mongodb-native/commit/b0f83b84e4f519083342cc971f5940a38110d58f) refactor: notify when attempting to use deprecated events/options
- [`3b076b3`](https://github.com/mongodb/node-mongodb-native/commit/3b076b37d6736f39acc223f40016411ce98477bd) fix(cursor): call `initialize` after session support check
- [`3471c28`](https://github.com/mongodb/node-mongodb-native/commit/3471c28532874955672c8705f12ad6f06e988ad7) fix(pool): support a `drain` event for use with unified topology
- [`c24eb91`](https://github.com/mongodb/node-mongodb-native/commit/c24eb910f0d508cf03967df3972d352fafc89038) test: add a color for workload messages to `sdam_viz`
- [`261f1e5`](https://github.com/mongodb/node-mongodb-native/commit/261f1e54c50a18396eb4db42c5ee7f4f73f84773) fix(topology): don't drain iteration timers on server selection
- [`b425fe5`](https://github.com/mongodb/node-mongodb-native/commit/b425fe5e602d2810bb07e89b83e2922220fc7032) refactor(topology): remove extra timers around selection monitoring
- [`2d976bd`](https://github.com/mongodb/node-mongodb-native/commit/2d976bdba31ce4c12c6056ce8bd1fc897a76fadf) fix(topology): correct logic for checking for sessions support
- [`4d2bd6e`](https://github.com/mongodb/node-mongodb-native/commit/4d2bd6eb70fe66a3f93d167536f30a301d84d493) test: remove use of `format` in max staleness tests
- [`28a944b`](https://github.com/mongodb/node-mongodb-native/commit/28a944ba576ba85e45ffa9a30ef6109254bc57e0) refactor: minor modification to the workload generator for sdam_viz
- Additional commits viewable in [compare view](https://github.com/mongodb/node-mongodb-native/compare/v3.3.3...v3.3.5)
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 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 the `.dependabot/config.yml` file in this repo:
- Update frequency
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps mongodb from 3.3.3 to 3.3.5.
Release notes
*Sourced from [mongodb's releases](https://github.com/mongodb/node-mongodb-native/releases).* > ## v3.3.5 > The MongoDB Node.js team is pleased to announce version 3.3.5 of the driver > > ## Release Highlights > > ### unified topology > This patch release includes additional fixes for the regression in the unified topology discovered in v3.3.2, expanding our testing infrastructure to include a simulated workload during failover testing. There was a bug when connecting to single-node replicasets which could result in a stack overflow which was corrected. Additionally, events and options which are incompatible with the unified topology will now emit a warning message. > > ### mongodb+srv > The release also includes a fix submitted by [@mpilar](https://github.com/mpilar), who found an inconsistency in our implementation of the "Initial Seedlist Discovery" specification. An `authSource` specified in the options passed to `MongoClient` would be overridden by an `authSource` provided in the TXT record checked during initial seedlist discovery over SRV. Thank you very much Miguel! > > ### bulkWrite > `BulkWriteError` is now exported at the top level of the module so that users can catch them easily. Additionally, a fix was made to ensure that the index of operations passed into an `unordered` bulk operation were preserved when reporting possible errors in the future. > > ## Release Notes >Bug >
>>- [NODE-1747] - Replica set causes MongoNetworkError due to not connecting with fully qualified domain name
>
> - [NODE-2089] - Only apply TransientTransactionError label within a transaction
>
> - [NODE-2143] - getaddrinfo ENOTFOUND error on Windows 10 due to failed fallback to ipv4 after ipv6 lookup fails
>
> - [NODE-2308] - Bulk write error returns incorrect index in WriteError for unordered writes
>
> - [NODE-2332] - useUnifiedTopology - replicaset
>
> - [NODE-2335] - Node Driver does not follow Initial DNS Seedlist Discovery spec
>
> - [NODE-2342] - Enabling useUnifiedTopology results in stack overflow when connecting to uninitialized replica set
>
>
> >Improvement >
>>- [NODE-2348] - Document and notify on deprecated events and options for unified topology
>
> - [NODE-2306] - Driver module does not export `BulkWriteError`
>
>
> > > ## v3.3.4 > The MongoDB Node.js team is pleased to announce version 3.3.4 of the driver > > ## Release Highlights > This release primary consists of improvements to the "unified topology". In particular, a regression with interaction between the connection pool and topology could result in servers which "go away" (due to network error, for example) would not return, resulting in a `MongoTimeoutError`. > > ... (truncated)Commits
- [`6930e12`](https://github.com/mongodb/node-mongodb-native/commit/6930e1265c1dae7a5c219b993be1f90b28a40851) chore(release): 3.3.5 - [`b0f83b8`](https://github.com/mongodb/node-mongodb-native/commit/b0f83b84e4f519083342cc971f5940a38110d58f) refactor: notify when attempting to use deprecated events/options - [`3b076b3`](https://github.com/mongodb/node-mongodb-native/commit/3b076b37d6736f39acc223f40016411ce98477bd) fix(cursor): call `initialize` after session support check - [`3471c28`](https://github.com/mongodb/node-mongodb-native/commit/3471c28532874955672c8705f12ad6f06e988ad7) fix(pool): support a `drain` event for use with unified topology - [`c24eb91`](https://github.com/mongodb/node-mongodb-native/commit/c24eb910f0d508cf03967df3972d352fafc89038) test: add a color for workload messages to `sdam_viz` - [`261f1e5`](https://github.com/mongodb/node-mongodb-native/commit/261f1e54c50a18396eb4db42c5ee7f4f73f84773) fix(topology): don't drain iteration timers on server selection - [`b425fe5`](https://github.com/mongodb/node-mongodb-native/commit/b425fe5e602d2810bb07e89b83e2922220fc7032) refactor(topology): remove extra timers around selection monitoring - [`2d976bd`](https://github.com/mongodb/node-mongodb-native/commit/2d976bdba31ce4c12c6056ce8bd1fc897a76fadf) fix(topology): correct logic for checking for sessions support - [`4d2bd6e`](https://github.com/mongodb/node-mongodb-native/commit/4d2bd6eb70fe66a3f93d167536f30a301d84d493) test: remove use of `format` in max staleness tests - [`28a944b`](https://github.com/mongodb/node-mongodb-native/commit/28a944ba576ba85e45ffa9a30ef6109254bc57e0) refactor: minor modification to the workload generator for sdam_viz - Additional commits viewable in [compare view](https://github.com/mongodb/node-mongodb-native/compare/v3.3.3...v3.3.5)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 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 the `.dependabot/config.yml` file in this repo: - Update frequency - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)