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 6.2.0 to 6.5.0 #40

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

[Snyk] Upgrade mongodb from 6.2.0 to 6.5.0 #40

wants to merge 1 commit into from

Conversation

lydmoon
Copy link
Owner

@lydmoon lydmoon commented May 19, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade mongodb from 6.2.0 to 6.5.0.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ 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 59 versions ahead of your current version.

  • The recommended version was released 2 months ago, on 2024-03-11.

Release notes
Package name: mongodb
  • 6.5.0 - 2024-03-11

    6.5.0 (2024-03-11)

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

    Release Notes

    Bulk Write Operations Generate Ids using pkFactory

    When performing inserts, the driver automatically generates _ids for each document if there is no _id present. By default, the driver generates ObjectIds. An option, pkFactory, can be used to configure the driver to generate _ids that are not object ids.

    For a long time, only Collection.insert and Collection.insertMany actually used the pkFactory, if configured. Notably, Collection.bulkWrite(), Collection.initializeOrderedBulkOp() and Collection.initializeOrderedBulkOp() always generated ObjectIds, regardless of what was configured on collection.

    The driver always generates _ids for inserted documents using the pkFactory.

    Caution

    If you are using a pkFactory and performing bulk writes, you may have inserted data into your database that does not have _ids generated by the pkFactory.

    Fixed applying read preference to commands depending on topology

    When connecting to a secondary in a replica set with a direct connection, if a read operation is performed, the driver attaches a read preference of primaryPreferred to the command.

    Fixed memory leak in Connection layer

    The Connection class has recently been refactored to operate on our socket operations using promises. An oversight how we made async network operations interruptible made new promises for every operation. We've simplified the approach and corrected the leak.

    Query SRV and TXT records in parallel

    When connecting using a convenient SRV connection string (mongodb+srv://) hostnames are obtained from an SRV dns lookup and some configuration options are obtained from a TXT dns query. Those DNS operations are now performed in parallel to reduce first-time connection latency.

    Container and Kubernetes Awareness

    The Node.js driver now keeps track of container metadata in the client.env.container field of the handshake document.

    If space allows, the following metadata will be included in client.env.container:

    env?: { 
  container?: {
    orchestrator?: 'kubernetes' // if process.env.KUBERNETES_SERVICE_HOST is set
    runtime?: 'docker' // if the '/.dockerenv' file exists
  } 
}

    Note: If neither Kubernetes nor Docker is present, client.env will not have the container property.

    Add property errorResponse to MongoServerError

    The MongoServer error maps keys from the error document returned by the server on to itself. There are some use cases where the original error document is desirable to obtain in isolation. So now, the mongoServerError.errorResponse property stores a reference to the error document returned by the server.

    Deprecated unused CloseOptions interface

    The CloseOptions interface was unintentionally made public and was only intended for use in the driver's internals. Due to recent refactoring (NODE-5915), this interface is no longer used in the driver. Since it was marked public, out of an abundance of caution we will not be removing it outside of a major version, but we have deprecated it and will be removing it in the next major version.

    Features

    Bug Fixes

    Performance Improvements

    Documentation

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

  • 6.5.0-dev.20240503.sha.7f191cf - 2024-05-03
  • 6.5.0-dev.20240502.sha.9d73f45 - 2024-05-02
  • 6.5.0-dev.20240426.sha.6d8ad33 - 2024-04-26
  • 6.5.0-dev.20240424.sha.6abc074 - 2024-04-24
  • 6.5.0-dev.20240423.sha.4a62ec6 - 2024-04-23
  • 6.5.0-dev.20240420.sha.eece8c1 - 2024-04-20
  • 6.5.0-dev.20240419.sha.c213679 - 2024-04-19
  • 6.5.0-dev.20240418.sha.af18c53 - 2024-04-18
  • 6.5.0-dev.20240417.sha.f1f816f - 2024-04-17
  • 6.5.0-dev.20240416.sha.6248174 - 2024-04-16
  • 6.5.0-dev.20240413.sha.8845206 - 2024-04-13
  • 6.5.0-dev.20240412.sha.232bf3c - 2024-04-12
  • 6.5.0-dev.20240411.sha.ddd1e81 - 2024-04-11
  • 6.5.0-dev.20240409.sha.30cac05 - 2024-04-09
  • 6.5.0-dev.20240406.sha.62ea94b - 2024-04-06
  • 6.5.0-dev.20240405.sha.ce55ca9 - 2024-04-05
  • 6.5.0-dev.20240404.sha.0e3d6ea - 2024-04-04
  • 6.5.0-dev.20240403.sha.cb5903f - 2024-04-03
  • 6.5.0-dev.20240328.sha.458cf6d - 2024-03-28
  • 6.5.0-dev.20240326.sha.918fe69 - 2024-03-26
  • 6.5.0-dev.20240323.sha.d94439f - 2024-03-23
  • 6.5.0-dev.20240322.sha.a8670a7 - 2024-03-22
  • 6.5.0-dev.20240321.sha.1879a04 - 2024-03-21
  • 6.5.0-dev.20240320.sha.8b91c30 - 2024-03-20
  • 6.5.0-dev.20240319.sha.0ebc1ac - 2024-03-19
  • 6.5.0-dev.20240316.sha.159ea81 - 2024-03-16
  • 6.5.0-dev.20240315.sha.77d0b47 - 2024-03-15
  • 6.5.0-dev.20240314.sha.8ab2055 - 2024-03-14
  • 6.5.0-dev.20240312.sha.55abb4b - 2024-03-12
  • 6.4.0 - 2024-02-29

    6.4.0 (2024-02-29)

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

    Release Notes

    Server selection will use a different Mongos on retry

    When retrying reads or writes on a sharded cluster, the driver will attempt to select a different mongos for the retry if multiple are present. This should heuristically avoid encountering the original error that caused the need to retry the operation.

    Caching AWS credentials provider per client

    Instead of creating a new AWS provider for each authentication, we cache the AWS credentials provider per client to prevent overwhelming the auth endpoint and ensure that cached credentials are not shared with other clients.

    BSON upgraded to ^6.4.0

    BSON has had a number of performance increases in the last two releases (6.3.0 and 6.4.0). Small basic latin (ASCII) only strings, small memory allocations (ObjectId and Decimal128) and numeric parsing operations (int32, doubles, and longs) have all had optimizations applied to them.

    For details check out the release notes here: BSON 6.3.0 and BSON 6.4.0 🐎

    ExceededTimeLimit was made a retryable reads error

    Read operations will be retried after receiving an error with the ExceededTimeLimit label.

    Fixed unresolved request issue in KMS requester

    Internal to the field-level encryption machinery is a helper that opens a TLS socket to the KMS provider endpoint and submits a KMS request. The code neglected to add a 'close' event listener to the socket, which had the potential to improperly leave the promise pending indefinitely if no error was encountered.

    The base64 padding is now preserved in the saslContinue command

    The authentication was rejected by the saslContinue command from mongosh due to missing "=" padding from the client. We fixed the way we parse payload to preserve trailing "="s.

    countDocuments now types the filter using the collection Schema

    Previously, countDocuments had a weakly typed Document type for the filter allowing any JS object as input. The filter is now typed as Filter<Schema> to enable autocompletion, and, hopefully, catch minor bugs.

    Thank you to @ pashok88895 for contributing to this improvement.

    The type error with $addToSet in bulkWrite was fixed

    Previously the following code sample would show a type error:

    interface IndexSingatureTestDocument extends Document {
    readonly myId: number;
    readonly mySet: number[];
  }
const indexSingatureCollection = undefined as unknown as Collection<IndexSingatureTestDocument>;
indexSingatureCollection.bulkWrite([
  {
    updateOne: {
      filter: { myId: 0 },
      update: {
        $addToSet: { mySet: 0 } // The type error! Type 'number' is not assignable to type 'never'.
      }
    }
  }
]);

    It happened because the driver's Document type falls back to any, and internally we could not distinguish whether or not this assignment was intentional and should be allowed.

    After this change, users can extend their types from Document/any, or use properties of any type and we skip the $addToSet validation in those cases.

    Fixed heartbeat duration including socket creation

    The ServerHeartbeatSucceeded and ServerHeartbeatFailed event have a duration property that represents the time it took to perform the hello handshake with MongoDB. The Monitor responsible for issuing heartbeats mistakenly included the time it took to create the socket in this field, which inflates the value with the time it takes to perform a DNS lookup, TCP, and TLS handshakes.

    Errors on cursor transform streams are now properly propagated.

    These were previously swallowed and now will be emitted on the error event:

    const transform = new Transform({
  transform(data, encoding, callback) {
    callback(null, data);
  },
});
const stream = db.collection('tests').find().sort({ studentId: -1 }).stream({ transform });
stream.on('error', err => {
  // The error will properly be emitted here.
});

    The AWS token is now optional

    Users may provide an AWS_SESSION_TOKEN as a client option or AWS configuration in addition to a username and password. But if the token is not provided, the driver won't throw an exception and let AWS SDK handle the request.

    Features

    Bug Fixes

    Performance Improvements

    Documentation

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

  • 6.4.0-dev.20240307.sha.28b7040 - 2024-03-07
  • 6.4.0-dev.20240306.sha.057c223 - 2024-03-06
  • 6.4.0-dev.20240305.sha.eab8f23 - 2024-03-05
  • 6.4.0-dev.20240301.sha.f2b3484 - 2024-03-01
  • 6.3.0 - 2023-11-16

    6.3.0 (2023-11-15)

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

    Release Notes

    New client option serverMonitoringMode

    For users that want to control the behaviour of the monitoring connection between each node in the topology, a new option, serverMonitoringMode, has been added. This defaults to auto but can be forced into a specific mode by providing a value of poll or stream. When the setting is auto the monitoring mode will be determined by the environment the driver is running in, specifically, FaaS environments prefer "polling" mode and all others prefer "streaming".

    A polling monitor periodically issues a hello command to the node at an interval of heartbeatFrequencyMS. A streaming monitor sends an initial hello and then will automatically get a response from the Node when a change in server configuration occurs or at a maximum time of heartbeatFrequencyMS. The value of that option defaults to 10000 milliseconds.

    This new option can be provided in the connection string or as an option to the MongoClient.

    // In the connection string.
    new MongoClient('mongodb://127.0.0.1:27017/?serverMonitoringMode=stream');

    // In the options
    new MongoClient('mongodb://127.0.0.1:27017/', { serverMonitoringMode: 'stream' });

    Fix connection leak when serverApi is enabled

    When enabling serverApi the driver's RTT measurement logic (used to determine the closest node) still sent the legacy hello command "isMaster" causing the server to return an error. Unfortunately, the error handling logic did not correctly destroy the socket which would cause a leak.

    Both sending the correct hello command and the error handling connection clean-up logic are fixed in this change.

    GridFS fields deprecated

    The GridFS contentType and aliases options are deprecated. According to the GridFS spec, applications wishing to store contentType and aliases should add a corresponding field to the metadata document instead.

    Remove deprecation warning about punycode

    The mongodb-connection-string-url package which parses connection strings relied on Node's punycode module, the package now imports the community package removing the deprecation warning on Node.js 20+.

    Features

    Bug Fixes

    Documentation

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

  • 6.3.0-dev.20240229.sha.99a0059 - 2024-02-29
  • 6.3.0-dev.20240228.sha.f26de76 - 2024-02-28
  • 6.3.0-dev.20240227.sha.09c9b0b - 2024-02-27
  • 6.3.0-dev.20240224.sha.233a2e0 - 2024-02-24
  • 6.3.0-dev.20240223.sha.17952d2 - 2024-02-23
  • 6.3.0-dev.20240222.sha.46b7bbb - 2024-02-22
  • 6.3.0-dev.20240221.sha.38742c2 - 2024-02-21
  • 6.3.0-dev.20240220.sha.90cb6fa - 2024-02-20
  • 6.3.0-dev.20240216.sha.10a5c5a - 2024-02-16
  • 6.3.0-dev.20240214.sha.ecfc615 - 2024-02-14
  • 6.3.0-dev.20240210.sha.a63fbc2 - 2024-02-10
  • 6.3.0-dev.20240209.sha.ca3780a - 2024-02-09
  • 6.3.0-dev.20240202.sha.9401d09 - 2024-02-02
  • 6.3.0-dev.20240131.sha.a42039b - 2024-01-31
  • 6.3.0-dev.20240127.sha.b7d28d3 - 2024-01-27
  • 6.3.0-dev.20240126.sha.8f7bb59 - 2024-01-26
  • 6.3.0-dev.20240125.sha.38fb2e4 - 2024-01-25
  • 6.3.0-dev.20240123.sha.7f97c2a - 2024-01-23
  • 6.3.0-dev.20240120.sha.f506b6a - 2024-01-20
  • 6.3.0-dev.20240119.sha.9b76a43 - 2024-01-19
  • 6.3.0-dev.20240113.sha.86e2659 - 2024-01-13
  • 6.3.0-dev.20240110.sha.8504d91 - 2024-01-10
  • 6.3.0-dev.20240108.sha.7f3ce0b - 2024-01-08
  • 6.2.0 - 2023-10-20

    6.2.0 (2023-10-19)

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

    Release Notes

    Updated to BSON 6.2.0

    BSON now prints in full color! 🌈 🚀

    See our release notes for BSON 6.2.0 here for more examples!

    insertedIds in bulk write now contain only successful insertions

    Prior to this fix, the bulk write error's result.insertedIds property contained the _id of each attempted insert in a bulk operation.

    Now, when a bulkwrite() or an insertMany() operation rejects one or more inserts, throwing an error, the error's result.insertedIds property will only contain the _id fields of successfully inserted documents.

    Fixed edge case leak in findOne()

    When running a findOne against a time series collection, the driver left the implicit session for the cursor un-ended due to the way the server returns the resulting cursor information. Now the cursor will always be cleaned up regardless of the outcome of the find operation.

    Removed client-side collection and database name validation

    Database and collection name checking will now be in sync with the MongoDB server's naming restrictions. Specifically, users can now create collections that start or end with the '.' character.

    Features

    Bug Fixes

    Documentation

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

from mongodb GitHub release notes
Commit messages
Package name: mongodb
  • c9e32ad chore(main): release 6.5.0 [skip-ci] (#4013)
  • f6cd8d9 feat(NODE-6008): deprecate CloseOptions interface (#4030)
  • 36fa752 refactor(NODE-5915): topology close logic to be synchronous (#4021)
  • 937c9c8 fix(NODE-5981): read preference not applied to commands properly (#4010)
  • 31f1eed test(NODE-5969): convert CSFLE corpus test [Snyk] Upgrade react-router-dom from 6.18.0 to 6.19.0 #6 to TS, async/await and add write concerns to all CRUD operations (#4029)
  • fbb5059 fix(NODE-5636): generate _ids using pkFactory in bulk write operations (#4025)
  • 2348548 test(DRIVERS-2812): sdam load balancer tests in serverless (#4026)
  • c023242 feat(NODE-5988): Provide access to raw results doc on MongoServerError (#4016)
  • 69de253 fix(NODE-5993): memory leak in the `Connection` class (#4022)
  • 28b7040 feat(NODE-5968): container and Kubernetes awareness in client metadata (#4005)
  • e30c6d3 chore(NODE-5997): update saslprep to ^1.1.5 (#4023)
  • 4ac9675 test(NODE-5962): gossip cluster time in utr (#4019)
  • 057c223 fix(NODE-5985): throw Nodejs' certificate expired error when TLS fails to connect instead of `CERT_HAS_EXPIRED` (#4014)
  • 7eaf2c8 refactor(NODE-5903): add newline to stdio logging (#4018)
  • 443835e test(NODE-5992): fix env var restoration in tests (#4017)
  • eab8f23 perf(NODE-5986): parallelize SRV/TXT resolution (#4012)
  • f2b3484 docs: generate 6.4.0 documentation (#4008)
  • 9ac2e38 chore(main): release 6.4.0 [skip-ci] (#3935)
  • 5f62f56 docs: generate docs from latest main [skip-ci] (#3977)
  • 90f2f70 feat(NODE-5978): upgrade BSON to ^6.4.0 (#4007)
  • 99a0059 test(NODE-5731): add serverless proxy testing (#4003)
  • 1ca6269 test(NODE-5929): convert txn legacy spec tests (#3987)
  • f26de76 fix(NODE-5944): make AWS session token optional (#4002)
  • 09c9b0b chore(NODE-5972): specify TS 5.0 in package.json and package-lock (#4004)

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

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

@snyk-bot
fix: upgrade mongodb from 6.2.0 to 6.5.0
5934aa6 
Snyk has created this PR to upgrade mongodb from 6.2.0 to 6.5.0.

See this package in npm:
mongodb

See this project in Snyk:
https://app.snyk.io/org/lydiamoon7/project/db315a82-4a35-495f-9f45-8c58e365dfea?utm_source=github&utm_medium=referral&page=upgrade-pr
@lydmoon lydmoon self-assigned this May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@lydmoon lydmoon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@lydmoon @snyk-bot