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.

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

[Snyk] Upgrade mongodb from 3.6.0 to 3.7.1 #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade mongodb from 3.6.0 to 3.7.1 #5

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Oct 8, 2021

Snyk has created this PR to upgrade mongodb from 3.6.0 to 3.7.1.

merge advice
ℹ️ 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.

  • The recommended version is 14 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2021-09-14.
Release notes
Package name: mongodb
  • 3.7.1 - 2021-09-14

    The MongoDB Node.js team is pleased to announce version 3.7.1 of the mongodb package!

    Release Highlights

    This release contains an internal improvement that makes our monitor utilize the new hello handshake for monitoring when available.

    Features

    Documentation

    We invite you to try the mongodb library immediately, and report any issues to the NODE project.

  • 3.7.0 - 2021-08-31

    The MongoDB Node.js team is pleased to announce version 3.7.0 of the mongodb package!

    Release Highlights

    Versioned API

    Versioned API is a new feature in MongoDB 5.0 that allows user-selectable API versions, subsets of MongoDB server semantics, to be declared on a client. During communication with a server, clients with a declared API version will force the server to behave in a manner compatible with the API version. Declaring an API version on a client can be used to ensure consistent responses from a server, providing long term API stability for an application. The declared API version is applied to all commands run through the client, including those sent through the generic RunCommand helper. Specifying versioned API options in the command document AND declaring an API version on the client is not supported and will lead to undefined behavior.

    Declare an API version on a client

    // Declare API version "1" for the client
    client = new MongoClient(uri, { serverApi: { version: '1' } });

    cursor = client.db('database').collection('coll').find(...);

    Strict mode

    Declaring a strict API version will cause the MongoDB server to reject all commands that are not part of the declared API version. This includes command options and aggregation pipeline stages. For example, the following find call would fail because the tailable option is not part of version 1:

    // Declare API version "1" for the client, with strict on
    client = new MongoClient(uri, { serverApi: { version: '1', strict: true } });

    // Fails with an error
    cursor = client.db('database').collection('coll').find({ ... }, { tailable: true });

    Deprecation Errors

    The deprecationErrors option can be used to enable command failures when using functionality that is deprecated from version 1. Note that at the time of this writing, no deprecations in version 1 exist.

    // Declare API version "1" for the client, with deprecationErrors on
    client = new MongoClient(uri, { serverApi: { version: '1', deprecationErrors: true } });

    // Note: since API version "1" is the initial version, there are no deprecated commands to provide as an example yet.

    Features

    Bug Fixes

    Documentation

    We invite you to try the mongodb library immediately, and report any issues to the NODE project.

  • 3.6.12 - 2021-08-30

    The MongoDB Node.js team is pleased to announce version 3.6.12 of the mongodb package!

    Bug Fixes

    Documentation

    We invite you to try the mongodb library immediately, and report any issues to the NODE project.

  • 3.6.11 - 2021-08-05

    The MongoDB Node.js team is pleased to announce version 3.6.11 of the mongodb package!

    Release Highlights

    This patch addresses a few bugs listed below.
    Notably, we fixed an issue with the way we imported one of our optional dependencies that blocked webpack bundling.

    If you are a webpack user you will still get warnings for our optional dependencies (if you don't use them).
    You can hush the warnings by adding this option to your webpack config:

    {
    // ...
    externals: [
        'mongodb-client-encryption',
        'aws4',
        'saslprep',
        'kerberos',
        'snappy',
        'bson-ext',
    ],
    // ...
}

    It is important to note that this will leave the imports in place and not pull in the code to your bundle. If you later do adopt using these dependencies you'll want to revert the relevant setting.

    Bug Fixes

    Documentation

    We invite you to try the mongodb package immediately, and report any issues to the NODE project.

  • 3.6.10 - 2021-07-06

    The MongoDB Node.js team is pleased to announce version 3.6.10 of the mongodb package!

    Release Highlights

    This patch addresses a few bugs listed below. Notably the bsonRegExp option is now respected by the underlying BSON library, you can use this to decode regular expressions that contain syntax not permitted in native JS RegExp objects. Take a look at this example:

    await collection.insertOne({ a: new BSONRegExp('(?-i)AA_') })
await collection.findOne({ a: new BSONRegExp('(?-i)AA_') }, { bsonRegExp: true })
// { _id: ObjectId,  a: BSONRegExp { pattern: '(?-i)AA_', options: '' } }

    Also there was an issue with Cursor.forEach where user defined forEach callbacks that throw errors incorrectly handled catching errors. Take a look at the comments in this example:

    collection.find({}).forEach(doc => {
    if(doc.bad) throw new Error('bad document!');
}).catch(error => {
    // now this is called! and error is `bad document!`
})
// before this fix the `bad document!` error would be thrown synchronously
// and have to be caught with try catch out here

    Bug Fixes

    Documentation

    We invite you to try the mongodb package immediately, and report any issues to the NODE project.

  • 3.6.9 - 2021-05-26
  • 3.6.8 - 2021-05-21
  • 3.6.7 - 2021-05-18
  • 3.6.6 - 2021-04-06
  • 3.6.5 - 2021-03-16
  • 3.6.4 - 2021-02-02
  • 3.6.3 - 2020-11-06
  • 3.6.2 - 2020-09-10
  • 3.6.1 - 2020-09-02
  • 3.6.0 - 2020-07-30
from mongodb GitHub release notes
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@snyk-bot