search

ioBroker / ioBroker.node-red

Instantiate the server with node-red
Apache License 2.0
52 stars 30 forks source link

Bump mongodb from 3.7.1 to 4.1.2 #220

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps mongodb from 3.7.1 to 4.1.2.

Release notes

Sourced from mongodb's releases.

v4.1.2

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

Release Highlights

This release addresses a number of bug fixes, please peruse the list below for more information on each fix.

Bug Fixes

  • NODE-3434: errInfo should be exposed on bulk write (#2977) (6b3c161)
  • NODE-3467: allow object type for aggregate out helper (#2971) (cd603e8)
  • NODE-3487: check for nullish aws mechanism property (#2951) (78ec0dd)
  • NODE-3559: incorrect GridFS stream type (#2981) (3915ea8)
  • NODE-3567: correct typing on aggregation out helper (#2967) (a299a0b)
  • NODE-3574: reintroduce ObjectID export (#2965) (2291119)
  • NODE-3585: MongoClientOptions#compressors has incorrect type (#2976) (f1b896d)
  • NODE-3591: tlsCertificateKeyFile option does not default cert (#2979) (6d42267)
  • NODE-3599: incorrect indexes return type (#2980) (122b9f3)

Documentation

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

v4.1.1

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

Release Highlights

Error handling

We introduced better organization and consistency to our existing errors in an effort to provide more detailed error types that can help identify issues clearly and quickly. Our readme has a new section that describes how to handle errors thrown by the driver and defines our approach to semver in the context of errors. Notably, we recommend only using instanceof checks to filter for a given error class as we do not guarantee error messages or names will be preserved between patch releases, only the subclass hierarchy.

Thanks so much to our summer interns @​andymina and @​W-A-James for undertaking this effort!

Notable fixes

  • This version of the driver brings in the latest BSON release which includes deserialization performance improvements.
  • The snappy package recently released a major version bump (v7) that makes use of a rust implementation of Snappy compression. Our driver can now make use of this version (while maintaining compatibility with the previous v6).
  • findOne() once again correctly returns null when no match is found instead of undefined. This change was unintentional and not consistent with our other APIs. It slipped through testing due to the nature of undefined and null being nearly (==) but not actually (===) equal. We apologize if this results in the need for any code changes.

This release also addresses some Typescript issues that require further explanation, let's dive in:

TypeScript support

Projections

... (truncated)

Changelog

Sourced from mongodb's changelog.

Changes in 4.x (and how to migrate!)

Hello dear reader, thank you for adopting version 4.x of the MongoDB Node.js driver, from the bottom of our developer hearts we thank you so much for taking the time to upgrade to our latest and greatest offering of a stunning database experience. We hope you enjoy your upgrade experience and this guide gives you all the answers you are searching for. If anything, and we mean anything, hinders your upgrade experience please let us know via JIRA. We know breaking changes are hard but they are sometimes for the best. Anyway, enjoy the guide, see you at the end!

Key Changes

Typescript

We've migrated the driver to Typescript! Users can now harness the power of type hinting and intellisense in editors that support it to develop their MongoDB applications. Even pure JavaScript projects can benefit from the type definitions with the right linting setup. Along with the type hinting there's consistent and helpful docs formatting that editors should be able to display while developing. Recently we migrated our BSON library to TypeScript as well, this version of the driver pulls in that change.

Community Types users (@​types/mongodb)

If you are a user of the community types (@​types/mongodb) there will likely be compilation errors while adopting the types from our codebase. Unfortunately we could not achieve a one to one match in types due to the details of writing the codebase in Typescript vs definitions for the user layer API along with the breaking changes of this major version. Please let us know if there's anything that is a blocker to upgrading on JIRA.

Node.js Version

We now require node 12.9 or greater for version 4 of the driver. If that's outside your support matrix at this time, that's okay! Bug fix support for our 3.x branch will not be ending until summer 2022, which has support going back as far as Node.js v4!

CRUD results

Our CRUD operations now return the drivers-wide spec-compliant results which are defined here:

For example, insertOne() used to return an object that was shaped like:

interface LegacyInsertOneResult {
    insertedCount: number;
    ops: InsertedDocument[];
    insertedId: ObjectId;
    connection: Connection;
    result: { ok: number; n: number };
}

and now returns:

</tr></table>

... (truncated)

Commits
  • 78df6b9 chore(release): 4.1.2
  • 4353bcf chore: add note about install Node.js type definitions (#2982)
  • 3915ea8 fix(NODE-3559): incorrect GridFS stream type (#2981)
  • 122b9f3 fix(NODE-3599): incorrect indexes return type (#2980)
  • 6d42267 fix(NODE-3591): tlsCertificateKeyFile option does not default cert (#2979)
  • 6b3c161 fix(NODE-3434): errInfo should be exposed on bulk write (#2977)
  • f1b896d fix(NODE-3585): MongoClientOptions#compressors has incorrect type (#2976)
  • cfdd799 chore(NODE-3293): update dependencies (#2975)
  • 2291119 fix(NODE-3574): reintroduce ObjectID export (#2965)
  • 1be8e93 chore(NODE-3293): update semver (#2973)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 3 years ago

Superseded by #225.