[Snyk] Upgrade mongodb from 3.7.3 to 4.3.1 #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade mongodb from 3.7.3 to 4.3.1. See this package in npm: https://www.npmjs.com/package/mongodb See this project in Snyk: https://app.snyk.io/org/purple-dobie/project/5b44f72e-7a88-48c5-88b3-9d88f5051998?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade mongodb from 3.7.3 to 4.3.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: mongodb
-
4.3.1 - 2022-01-18
- type checking defaults to
interface Node {
- indirectly self-referential types are still not supported
interface A {
- NODE-3792: remove offensive language throughout the codebase (#3091) (8e2b0cc)
- NODE-3852,NODE-3854,NODE-3856: Misc typescript fixes for 4.3.1 (#3102) (dd5195a)
- Reference: https://docs.mongodb.com/drivers/node
- API: https://mongodb.github.io/node-mongodb-native/4.3
- Changelog: https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md
-
4.3.0 - 2022-01-06
// disable UTF-8 validation globally on the MongoDB client
interface Human {
- If no
- If an
- If an
- NODE-3589: support dot-notation attributes in Filter (#2972) (76fff97)
- NODE-3633: add Socks5 support (#3041) (451627a)
- NODE-3784: Add
- gridfs: make
- NODE-2899: sort and correct circular imports (#3072) (48cc729)
- NODE-3675: SRV option bug correctly defaults authSource to $external (#3079) (30f2a2d)
- NODE-3803: Fix _id typing on collection create operations (#3077) (f1979db)
- Reference: https://docs.mongodb.com/drivers/node
- API: https://mongodb.github.io/node-mongodb-native/4.3
- Changelog: https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md
-
4.2.2 - 2021-12-13
- NODE-3705: ReadPreference.fromOptions omitting hedge and maxStalenessSeconds when readPreference is a string (#3060) (b9fbac5)
- NODE-3711: retry txn end on retryable write (#3045) (7b00d0f)
- NODE-3765: make replacement for replaceOne operations without _id (#3040) (e07e564)
- stricter protocol check in connection string (#3078) (bc05671)
- Reference: https://docs.mongodb.com/drivers/node
- API: https://mongodb.github.io/node-mongodb-native/4.2
- Changelog: https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md
-
4.2.1 - 2021-11-30
- NODE-2370: correct a return type of hasNext() (#3058) (b6a63df)
- NODE-3627: Enable flexible BSON validation for server error key containing invalid utf-8 (#3054) (7a507f0)
- NODE-3648: run get more ops through server selection (#3030) (268e211)
- NODE-3767: don't delete dbName if authSource is provided (#3055) (0a830e2)
- NODE-3770: Filter type uses WithId on the schema (#3053) (307d623)
- Reference: https://docs.mongodb.com/drivers/node
- API: https://mongodb.github.io/node-mongodb-native/4.2
- Changelog: https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md
-
4.2.0 - 2021-11-17
-
4.1.4 - 2021-11-03
-
4.1.3 - 2021-10-05
-
4.1.2 - 2021-09-14
-
4.1.1 - 2021-08-24
-
4.1.0 - 2021-08-03
-
4.0.1 - 2021-07-20
-
4.0.0 - 2021-07-13
-
4.0.0-beta.6 - 2021-07-01
-
4.0.0-beta.5 - 2021-05-26
-
4.0.0-beta.4 - 2021-05-18
-
4.0.0-beta.3 - 2021-04-06
-
4.0.0-beta.2 - 2021-03-16
-
4.0.0-beta.1 - 2021-02-02
-
4.0.0-beta.0 - 2021-01-19
-
3.7.3 - 2021-10-20
from mongodb GitHub release notesThe MongoDB Node.js team is pleased to announce version 4.3.1 of the mongodb package!
Release Highlights
In this patch release, we address the limitation introduced in 4.3.0 with the dot notation Typescript improvements and recursive types.
Namely, this fix removes compilation errors for self-referential types.
Note that this fix still has the following limitations:
anyafter the first level of recursion for self-referential typesnext: Node | null;
}
declare const collection: Collection<Node>;
// no error here even though
nextis of typeNode | nullcollection.find({
next: {
next: 'asdf'
}
});
b: B;
}
interface B {
a: A;
}
declare const mutuallyRecursive: Collection<A>;
// this will throw an error because there is indirect recursion
// between types (A depends on B which depends on A and so on)
mutuallyRecursive.find({});
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
The MongoDB Node.js team is pleased to announce version 4.3.0 of the mongodb package!
Release Highlights
This release includes SOCKS5 support and a couple of other important features and bug fixes that we hope will improve your experience with the node driver.
The SOCKS5 options can be configured via the
proxyHost,proxyPort,proxyPasswordandproxyUsernameoptions in the connection string passed to theMongoClientinstance. Big thanks to @ addaleax for helping with this feature!The other notable features address performance and TypeScript as detailed below.
Performance
The original release of the 4.x driver relied on a new version of the BSON library that enables UTF-8 validation by default, resulting in noticeable performance degradation over the 3.x driver when processing over string data. This release introduces an option to opt out of this validation by specifying
enableUtf8Validation: falseat the client, database, collection, or individual operation level.For example:
const client = new MongoClient('mongodb://localhost:27017', { enableUtf8Validation: false });
// disable UTF-8 validation for a particular operation
const client = new MongoClient('mongodb://localhost:27017');
const db = client.db('database name');
const collection = db.collection('collection name');
await collection.find({ name: 'John Doe'}, { enableUtf8Validation: false });
TypeScript
Type inference for nested documents
Thanks to an amazing contribution from @ avaly we now have support for key auto-completion and type hinting on nested documents! MongoDB permits using dotted keys to reference nested keys or specific array indexes within your documents as a shorthand for getting at keys beneath the top layer. Typescript's Template Literal types allow us to take the interface defined on a collection and calculate at compile time the nested keys and indexes available.
For example:
name: string;
age: number;
}
interface Pet {
name: string
bestFriend: Human
}
const pets = client.db().collection<Pet>('pets');
await pets.findOne({ 'bestFriend.age': 'young!' }) // typescript error!
Here's what autocomplete suggests in VSCode:
WARNING: There is a known shortcoming to this feature: recursive types can no longer be used in your schema. For example, an interface that references itself or references another schema that references back to the root schema cannot be used on our
Collectiongeneric argument. Unlike at runtime where a "recursive" shaped document has an eventual stopping point we don't have the tools within the language to declare a base case enumerating nested keys. We hope this does not cause friction when upgrading driver versions: please do not hesitate to reach out with any feedback you have about this feature.Consistent type inference for the _id type
We have also enhanced the type inference for the
_idtype. Now, when performing operations on a collection, the following holds true based on the type of the schema:_idis specified on the schema, it is inferred to be of typeObjectIdand is optional on inserts._idis specified on the schema as required, then the_idtype is inferred to be of the specified type and is required on inserts._idis specified on the schema as optional, it is inferred to be of the specified type and is optional on inserts: this format is intended to be used with thepkFactoryoption in order to ensure a consistent_idis assigned to every new document.Features
enableUtf8Validationoption (#3074) (4f56409)Bug Fixes
GridFSBucketWriteStream.prototype.end()returnthisfor compat with @ types/[email protected] (#3088) (7bb9e37)Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
The MongoDB Node.js team is pleased to announce version 4.2.2 of the mongodb package!
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
The MongoDB Node.js team is pleased to announce version 4.2.1 of the mongodb package!
Release Highlights
This release fixes an issue with the dbName being overridden by the authSource option. Additionally, we have ensured that cursors re-run server selection when fetching additional batches, which should reduce issues encountered in long running function as a service environments.
Bug Fixes
Documentation
We invite you to try the mongodb library immediately, and report any issues to the NODE project.
Read more
Read more
Read more
Read more
Read more
Commit messages
Package name: mongodb
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs