[Snyk] Upgrade mongodb from 6.2.0 to 6.3.0

ladunjexa commented 7 months ago

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.3.0.

:information_source: 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 **24 versions** ahead of your current version. - The recommended version was released **4 months ago**, on 2023-11-16.

Release notes

Package name: mongodb

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
- NODE-3881: require hello command + OP_MSG when 'loadBalanced=True' (#3907) (fd58eec)
- NODE-5197: add server monitoring mode (#3899) (ae4c94a)
- NODE-5590: deprecate GridFS fields (#3905) (d2225da)
Bug Fixes
- NODE-4863: do not use RetryableWriteError for non-server errors (#3914) (08c9fb4)
- NODE-5709: bump mongodb-connection-string-url to 3.0.0 (#3909) (1c3dc02)
- NODE-5749: RTTPinger always sends legacy hello (#3921) (ebbfb8a)
Documentation
- Reference
- API
- Changelog
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
- NODE-5613: add awaited field to SDAM heartbeat events (#3895) (b50aadc)
- update bson to 6.2.0 (#3898) (32b7176)
Bug Fixes
- NODE-5496: remove client-side collection and database name check validation (#3873) (98550c6)
- NODE-5628: bulkWriteResult.insertedIds does not filter out _ids that are not actually inserted (#3867) (09f2a67)
- NODE-5706: make findOne() close implicit session to avoid memory leak (#3897) (995d138)
Documentation
- Reference
- API
- Changelog
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

a837036 chore(main): release 6.3.0 [skip-ci] (#3904)
ebbfb8a fix(NODE-5749): RTTPinger always sends legacy hello (#3921)
ae4c94a feat(NODE-5197): add server monitoring mode (#3899)
08c9fb4 fix(NODE-4863): do not use RetryableWriteError for non-server errors (#3914)
54adc9f feat(NODE-4878): Add remaining log configurable client options (#3908)
c0506b1 docs(NODE-5730): update load balancer docs (#3910)
b602162 refactor(NODE-5696): add async-iterator based socket helpers (#3896)
89cb092 test(NODE-5732): update data lake test scripts (#3913)
fd58eec feat(NODE-3881): require hello command + OP_MSG when 'loadBalanced=True' (#3907)
bb5fa43 feat(NODE-5452): Logging Cosmos Document DB Info Message (#3902)
1c3dc02 fix(NODE-5709): bump mongodb-connection-string-url to 3.0.0 (#3909)
1f63704 test(NODE-5707): update aws ecs task definition (#3906)
d2225da feat(NODE-5590): deprecate GridFS fields (#3905)
f495abb feat(NODE-4849): Add Typescript support for log path in client options (#3886)
4125526 docs: 6.2.0 docs (#3903)

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](https://app.snyk.io/org/ladunjexa/project/18e3c3cf-cd62-4bc3-9e16-377f4559f279?utm_source=github&utm_medium=referral&page=upgrade-pr) 🛠 [Adjust upgrade PR settings](https://app.snyk.io/org/ladunjexa/project/18e3c3cf-cd62-4bc3-9e16-377f4559f279/settings/integration?utm_source=github&utm_medium=referral&page=upgrade-pr) 🔕 [Ignore this dependency or unsubscribe from future upgrade PRs](https://app.snyk.io/org/ladunjexa/project/18e3c3cf-cd62-4bc3-9e16-377f4559f279/settings/integration?pkg=mongodb&utm_source=github&utm_medium=referral&page=upgrade-pr#auto-dep-upgrades)

vercel[bot] commented 7 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextjs14-devoverflow	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 8, 2024 9:24pm

vercel[bot] commented 7 months ago

Deployment failed with the following error:

Resource is limited - try again in 17 hours (more than 100, code: "api-deployments-free-per-day").

ladunjexa / nextjs14-devoverflow