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.

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

Bump mongodb from 3.6.6 to 4.1.4 #129

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 4, 2021

Bumps mongodb from 3.6.6 to 4.1.4.

Release notes

Sourced from mongodb's releases.

v4.1.4

Release Highlights

This release includes a couple of bug fixes as noted below:

Bug Fixes

  • NODE-3515: do proper opTime merging in bulk results (#3012) (43300c3)
  • NODE-3668: compile error with OptionalId on TS 4.5 beta (#3004) (ee7f095)

Documentation

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

v4.1.3

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

Release Highlights

This release includes a couple of TypeScript fixes as noted below:

Bug Fixes

  • NODE-3609: correct listDatabases return type (#2986) (a8e9938)
  • NODE-3624: Incorrect default aggregation generic type (#2987) (440517e)

Documentation

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

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)

... (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
  • c01b0ad chore(release): 4.1.4
  • adb2259 chore: bump bson patch version (#3026)
  • 662902d chore(NODE-3736): fix drivers tools cloning (#3023) (#3024)
  • 43300c3 fix(NODE-3515): do proper opTime merging in bulk results (#3012)
  • ee7f095 fix(NODE-3668): compile error with OptionalId on TS 4.5 beta (#3004)
  • 0a66124 chore: improve PR template text (#3003)
  • 644ac56 chore(NODE-3552): test serverless behind a loadbalancer (#2997)
  • 681a181 docs(NODE-3610): update contributing guidelines (#3000)
  • 808d7da test(NODE-3606): legacy and new versions of the CSFLE library (#2999)
  • c8d81c3 chore: skip flaky should recover on error during initial connect test (#3001)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by dariakp, a new releaser for mongodb since your current version.


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)

Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 3.6.6 to 4.1.4.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/docs/CHANGES_4.0.0.md)
- [Commits](mongodb/node-mongodb-native@v3.6.6...v4.1.4)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Related to updating outdated dependencies label Nov 4, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Nov 18, 2021

Superseded by #130.

@dependabot dependabot bot closed this Nov 18, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/mongodb-4.1.4 branch November 18, 2021 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Related to updating outdated dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants