Skip to content

Upgrade MongoDB Node.js driver to 7.6+ for full MongoDB 9.0 compatibility #10754

Closed

Description

@ga262

New Feature / Enhancement Checklist

Current Limitation

Parse Server pins the MongoDB Node.js driver at mongodb@7.1.0 (unchanged in 9.10.3). MongoDB 9.0 is generally available, including on Atlas, and #10750 / #10751 add it to the CI matrix, but deployments on MongoDB 9.0 still talk to the database through a driver that MongoDB has not tested against 9.0.

According to MongoDB's official client library compatibility tables (Node.js driver vs MongoDB Server):

Node.js driver MongoDB 9.0 MongoDB 8.0 MongoDB 7.0
7.6 to 7.7 ✓ fully compatible ✓ ✓
7.3 to 7.5 ⊛ partially compatible ✓ ✓
6.9 to 7.2 (incl. 7.1.0) not tested ✓ ✓

The same page states:

If your application doesn't work with MongoDB 9.0, we recommend upgrading to a driver version that is fully compatible (✓) with it. For the Node.js driver, this includes version 7.6 or later.

Feature / Enhancement Description

Upgrade mongodb from 7.1.0 to 7.7.0, the latest 7.x release and fully compatible with MongoDB 9.0, 8.0 and 7.0.

  • Same major version, so no breaking API change is expected for the storage adapter.
  • mongodb@7.7.0 requires Node.js >=20.19.0, which Parse Server's engines already requires.
  • Lockfile impact is small: bson 7.3.1 → 7.3.3, @mongodb-js/saslprep 1.4.12 → 1.6.0, and the separate mongodb@7.5.0 copy nested under mongodb-runner is deduplicated.

Example Use Case

  1. A Parse Server deployment runs on a MongoDB Atlas cluster.
  2. The cluster is upgraded from MongoDB 8.0 to 9.0.
  3. Parse Server keeps working with a driver that MongoDB officially lists as fully compatible with 9.0, instead of an untested combination.

Alternatives / Workarounds

Applications can force the driver version with npm overrides in their own package.json:

"overrides": {
  "parse-server": { "mongodb": "7.7.0" }
}

This works, but it runs Parse Server with a driver version its own test suite does not cover, so an upstream upgrade is preferable.

3rd Party References

Activity

  1. parse-github-assistant commented on Oct 6, 2026

    @parse-github-assistant

    🚀 Thanks for opening this issue! We are excited about your ideas for improvement!

  2. mtrezza commented on Oct 7, 2026

    @mtrezza
    Member

    How's this related to #10750? MongoDB 9 compatiblity must be added in single PR, not half-added across various PR.

  3. ga262 commented on Oct 7, 2026

    @ga262
    Author

    Agreed, they're two halves of the same change. #10750 / #10751 add MongoDB 9 to the CI matrix and docs, while this issue covers the driver: mongodb@7.1.0 is listed as "not tested" against MongoDB 9.0, and 7.6+ is the first fully compatible range.
    I'll move the driver upgrade to mongodb@7.7.0 into #10751 so MongoDB 9 support lands in a single PR (CI matrix + driver + docs), and close this issue as a duplicate of #10750.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions