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, mongoose, node-telegram-bot-api, nodemon #16

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

[Snyk] Upgrade: mongodb, mongoose, node-telegram-bot-api, nodemon #16

wants to merge 1 commit into from
+94 −34

Conversation

Habibullohnuriddin
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯‍♂ The following dependencies are linked and will therefore be updated together.

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

Name Versions Released on

mongodb
from 6.6.2 to 6.8.0 | 39 versions ahead of your current version | 2 months ago
on 2024-06-27
mongoose
from 8.4.0 to 8.5.3 | 9 versions ahead of your current version | a month ago
on 2024-08-13
node-telegram-bot-api
from 0.65.1 to 0.66.0 | 1 version ahead of your current version | 4 months ago
on 2024-05-20
nodemon
from 3.1.0 to 3.1.4 | 4 versions ahead of your current version | 3 months ago
on 2024-06-20

Release notes
Package name: mongodb
  • 6.8.0 - 2024-06-27

    6.8.0 (2024-06-27)

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

    Release Notes

    Add ReadConcernMajorityNotAvailableYet to retryable errors

    ReadConcernMajorityNotAvailableYet (error code 134) is now a retryable read error.

    ClientEncryption.createDataKey() and other helpers now support named KMS providers

    KMS providers can now be associated with a name and multiple keys can be provided per-KMS provider. The following example configures a ClientEncryption object with multiple AWS keys:

    const clientEncryption = new ClientEncryption(keyVaultClient, {
    'aws:key1': {
    accessKeyId: ...,
    secretAccessKey: ...
    },
    'aws:key2': {
    accessKeyId: ...,
    secretAccessKey: ...
    },

    clientEncryption.createDataKey('aws:key-1', { ... });

    Named KMS providers are supported for azure, AWS, KMIP, local and gcp KMS providers. Named KMS providers cannot be used if the application is using the automatic KMS provider refresh capability.

    This feature requires mongodb-client-encryption>=6.0.1.

    KMIP data keys now support a delegated option

    When creating a KMIP data key, delegated can now be specified. If true, the KMIP provider will perform encryption / decryption of the data key locally, ensuring that the encryption key never leaves the KMIP server.

    clientEncryption.createDataKey('kmip', { masterKey: { delegated: true } } );

    This feature requires mongodb-client-encryption>=6.0.1.

    Cursor responses are now parsed lazily 🦥

    MongoDB cursors (find, aggregate, etc.) operate on batches of documents equal to batchSize. Each time the driver runs out of documents for the current batch it gets more (getMore) and returns each document one at a time through APIs like cursor.next() or for await (const doc of cursor).

    Prior to this change, the Node.js driver was designed in such a way that the entire BSON response was decoded after it was received. Parsing BSON, just like parsing JSON, is a synchronous blocking operation. This means that throughout a cursor's lifetime invocations of .next() that need to fetch a new batch hold up on parsing batchSize (default 1000) documents before returning to the user.

    In an effort to provide more responsiveness, the driver now decodes BSON "on demand". By operating on the layers of data returned by the server, the driver now receives a batch, and only obtains metadata like size, and if there are more documents to iterate after this batch. After that, each document is parsed out of the BSON as the cursor is iterated.

    A perfect example of where this comes in handy is our beloved mongosh! 💚

    test> db.test.find()
[
	{ _id: ObjectId('665f7fc5c9d5d52227434c65'), ... },
  ...
]
Type "it" for more

    That Type "it" for more message would now print after parsing only the documents displayed rather than after the entire batch is parsed.

    Add Signature to Github Releases

    The Github release for the mongodb package now contains a detached signature file for the NPM package (named
    mongodb-X.Y.Z.tgz.sig), on every major and patch release to 6.x and 5.x. To verify the signature, follow the instructions in the 'Release Integrity' section of the README.md file.

    The LocalKMSProviderConfiguration's key property accepts Binary

    A local KMS provider at runtime accepted a BSON Binary instance but the Typescript inaccurately only permitted Buffer and string.

    Clarified cursor state properties

    The cursor has a few properties that represent the current state from the perspective of the driver and server. This PR corrects an issue that never made it to a release but we would like to take the opportunity to re-highlight what each of these properties mean.

    • cursor.closed - cursor.close() has been called, and there are no more documents stored in the cursor.
    • cursor.killed - cursor.close() was called while the cursor still had a non-zero id, and the driver sent a killCursors command to free server-side resources
    • cursor.id == null - The cursor has yet to send it's first command (ex. find, aggregate)
    • cursor.id.isZero() - The server sent the driver a cursor id of 0 indicating a cursor no longer exists on the server side because all data has been returned to the driver.
    • cursor.bufferedCount() - The amount of documents stored locally in the cursor.

    Features

    Bug Fixes

    Documentation

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

  • 6.8.0-dev.20240910.sha.833eaa41 - 2024-09-10
  • 6.8.0-dev.20240907.sha.91ceaf05 - 2024-09-07
  • 6.8.0-dev.20240905.sha.65e0e15c - 2024-09-05
  • 6.8.0-dev.20240904.sha.fb13ebfd - 2024-09-04
  • 6.8.0-dev.20240830.sha.1f10bdf8 - 2024-08-30
  • 6.8.0-dev.20240829.sha.6d65ae77 - 2024-08-29
  • 6.8.0-dev.20240824.sha.40ace73c - 2024-08-24
  • 6.8.0-dev.20240822.sha.f5254030 - 2024-08-22
  • 6.8.0-dev.20240821.sha.55bdeaa9 - 2024-08-21
  • 6.8.0-dev.20240813.sha.b70c8850 - 2024-08-13
  • 6.8.0-dev.20240808.sha.5565d500 - 2024-08-08
  • 6.8.0-dev.20240802.sha.54efb7d4 - 2024-08-02
  • 6.8.0-dev.20240731.sha.b26c3280 - 2024-07-31
  • 6.8.0-dev.20240727.sha.e9025843 - 2024-07-27
  • 6.8.0-dev.20240725.sha.74916f29 - 2024-07-25
  • 6.8.0-dev.20240720.sha.357ca086 - 2024-07-20
  • 6.8.0-dev.20240717.sha.35d88404 - 2024-07-17
  • 6.8.0-dev.20240716.sha.4b219d36 - 2024-07-16
  • 6.8.0-dev.20240712.sha.320dde04 - 2024-07-12
  • 6.8.0-dev.20240710.sha.fb442edc - 2024-07-10
  • 6.8.0-dev.20240709.sha.9a5e6110 - 2024-07-09
  • 6.8.0-dev.20240703.sha.5abf5fca - 2024-07-03
  • 6.8.0-dev.20240702.sha.f48f8d36 - 2024-07-02
  • 6.8.0-dev.20240629.sha.d85f827a - 2024-06-29
  • 6.8.0-dev.20240628.sha.45bc0982 - 2024-06-28
  • 6.7.0 - 2024-05-29

    6.7.0 (2024-05-29)

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

    Release Notes

    Support for MONGODB-OIDC Authentication

    MONGODB-OIDC is now supported as an authentication mechanism for MongoDB server versions 7.0+. The currently supported facets to authenticate with are callback authentication, human interaction callback authentication, Azure machine authentication, and GCP machine authentication.

    Azure Machine Authentication

    The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required and another optional username can be provided. Example:

    const client = new MongoClient('mongodb+srv://<username>@<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<azure_token>,ENVIRONMENT:azure');
await client.connect();

    GCP Machine Authentication

    The MongoClient must be instantiated with authMechanism=MONGODB-OIDC in the URI or in the client options. Additional required auth mechanism properties of TOKEN_RESOURCE and ENVIRONMENT are required. Example:

    const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC&authMechanismProperties=TOKEN_RESOURCE:<gcp_token>,ENVIRONMENT:gcp');
await client.connect();

    Callback Authentication

    The user can provide a custom callback to the MongoClient that returns a valid response with an access token. The callback is provided as an auth mechanism property an has the signature of:

    const oidcCallBack = (params: OIDCCallbackParams): Promise<OIDCResponse> => {
    // params.timeoutContext is an AbortSignal that will abort after 30 seconds for non-human and 5 minutes for human.
    // params.version is the current OIDC API version.
    // params.idpInfo is the IdP info returned from the server.
    // params.username is the optional username.

    // Make a call to get a token.
    const token = ...;
    return {
    accessToken: token,
    expiresInSeconds: 300,
    refreshToken: token
    };
    }

    const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
    authMechanismProperties: {
    OIDC_CALLBACK: oidcCallback
    }
    });
    await client.connect();

    For callbacks that require human interaction, set the callback to the OIDC_HUMAN_CALLBACK property:

    const client = new MongoClient('mongodb+srv://<host>:<port>/?authMechanism=MONGODB-OIDC', {
  authMechanismProperties: {
    OIDC_HUMAN_CALLBACK: oidcCallback
  }
});
await client.connect();

    Fixed error when useBigInt64=true was set on Db or MongoClient

    Fixed an issue where when setting useBigInt64=true on MongoClients or Dbs an internal function compareTopologyVersion would throw an error when encountering a bigint value.

    Features

    Bug Fixes

    Documentation

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

  • 6.7.0-dev.20240627.sha.fb724eb6 - 2024-06-27
  • 6.7.0-dev.20240626.sha.4f32decc - 2024-06-26
  • 6.7.0-dev.20240625.sha.27cb35bb - 2024-06-25
  • 6.7.0-dev.20240621.sha.8fb43f86 - 2024-06-21
  • 6.7.0-dev.20240619.sha.8d5d9846 - 2024-06-19
  • 6.7.0-dev.20240618.sha.ec3cabaf - 2024-06-18
  • 6.7.0-dev.20240615.sha.465ffd97 - 2024-06-15
  • 6.7.0-dev.20240614.sha.3ed6a2ad - 2024-06-14
  • 6.7.0-dev.20240613.sha.c1af6adc - 2024-06-13
  • 6.7.0-dev.20240608.sha.0655c730 - 2024-06-08
  • 6.7.0-dev.20240607.sha.aa429f8c - 2024-06-07
  • 6.7.0-dev.20240530.sha.f56938f - 2024-05-30
  • 6.6.2 - 2024-05-15

    6.6.2 (2024-05-15)

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

    Release Notes

    Server Selection performance regression due to incorrect RTT measurement

    Starting in version 6.6.0, when using the stream server monitoring mode, heartbeats were incorrectly timed as having a duration of 0, leading to server selection viewing each server as equally desirable for selection.

    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
Package name: mongoose
  • 8.5.3 - 2024-08-13

    8.5.3 / 2024-08-13

    • fix(document): call required functions on subdocuments underneath nested paths with correct context #14801 #14788
    • fix(populate): avoid throwing error when no result and lean() set #14799 #14794 #14759 MohOraby
    • fix(document): apply virtuals to subdocuments if parent schema has virtuals: true for backwards compatibility #14774 #14771 #14623 #14394
    • types: make HydratedSingleSubdocument and HydratedArraySubdocument merge types instead of using & #14800 #14793
    • types: support schema type inference based on schema options timestamps as well #14773 #13215 ark23CIS
    • types(cursor): indicate that cursor.next() can return null #14798 #14787
    • types: allow mongoose.connection.db to be undefined #14797 #14789
    • docs: add schema type widening advice #14790 JstnMcBrd
  • 8.5.2 - 2024-07-30

    8.5.2 / 2024-07-30

    • perf(clone): avoid further unnecessary checks if cloning a primitive value #14762 #14394
    • fix: allow setting document array default to null #14769 #14717 #6691
    • fix(model): support session: null option for save() to opt out of automatic session option with transactionAsyncLocalStorage #14744 #14736
    • fix(model+document): avoid depopulating manually populated doc as getter value #14760 #14759
    • fix: correct shardkey access in buildBulkWriteOps #14753 #14752 adf0nt3s
    • fix(query): handle casting $switch in $expr #14755 #14751
    • types: allow calling SchemaType.cast() without parent and init parameters #14756 #14748 #9076
    • docs: fix a wrong example in v6 migration guide #14758 abdelrahman-elkady
  • 8.5.1 - 2024-07-12

    8.5.1 / 2024-07-12

    • perf(model): performance improvements for insertMany() #14724
    • fix(model): avoid leaving subdoc defaults on top-level doc when setting subdocument to same value #14728 #14722
    • fix(model): handle transactionAsyncLocalStorage option with insertMany() #14743
    • types: make _id required on Document type #14735 #14660
    • types: fix ChangeStream.close to return a Promise like the driver #14740 orgads
  • 8.5.0 - 2024-07-08
  • 8.4.5 - 2024-07-05
  • 8.4.4 - 2024-06-25
  • 8.4.3 - 2024-06-17
  • 8.4.2 - 2024-06-17
  • 8.4.1 - 2024-05-31
  • 8.4.0 - 2024-05-17
from mongoose GitHub release notes
Package name: node-telegram-bot-api
  • 0.66.0 - 2024-05-20
  • 0.65.1 - 2024-03-10
from node-telegram-bot-api GitHub release notes
Package name: nodemon from nodemon GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

@snyk-bot
fix: upgrade multiple dependencies with Snyk
9b78349 
Snyk has created this PR to upgrade:
  - mongodb from 6.6.2 to 6.8.0.
    See this package in npm: https://www.npmjs.com/package/mongodb
  - mongoose from 8.4.0 to 8.5.3.
    See this package in npm: https://www.npmjs.com/package/mongoose
  - node-telegram-bot-api from 0.65.1 to 0.66.0.
    See this package in npm: https://www.npmjs.com/package/node-telegram-bot-api
  - nodemon from 3.1.0 to 3.1.4.
    See this package in npm: https://www.npmjs.com/package/nodemon

See this project in Snyk:
https://app.snyk.io/org/habibullohnuriddin/project/b938bc1a-bb5a-4cec-a318-85091bbac466?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
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.

config.env should be overridden by runtime env variables Problem with Newley released types
2 participants
@Habibullohnuriddin @snyk-bot