Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5231

Drop support for Node versions < 16.latest

    • 3
    • Not Needed
    • Needed
    • Hide

      There will be Node version compatibility changes in the next major (v6) of the driver. We don't know exactly what these changes will be yet. Once we're finished with v6 changes, we will communicate any Node compatibility changes.

      Show
      There will be Node version compatibility changes in the next major (v6) of the driver. We don't know exactly what these changes will be yet. Once we're finished with v6 changes, we will communicate any Node compatibility changes.

      Use Case

      As a... Node.js driver developer
      I want... to remove testing for Node versions < 16.latest
      So that... we reduce unnecessary overhead of maintaining unsupported Node.js versions

      User Impact

      • Users adopting the latest driver will have to upgrade to a supported Node.js runtime version

      Dependencies

      • Shell

      Unknowns

      • How do we want to capture this in the official compat tables?

      Acceptance Criteria

      Implementation Requirements

      • Remove Node versions < 16.latest (16.20 as of the writing of this ticket) from our testing matrix for the upcoming major version releases of:
        • node driver main
        • legacy driver
        • js-bson
        • mongo client encryption
      • TS target = ES 2021

      Testing Requirements

      • If any CI tasks are using a hardcoded version 16, these tasks should be upgraded to Node 18+; the tests in these tasks should continue to pass
      • Node 16 should be removed from the matrix versions and be tested as a stand-alone configuration with rapid server version replica-set (and possibly lowest supported server version), with fle and auth enabled
        • smoke test strategy - we won't to do that in this ticket, as long as the CI doesn't break - we'll do it as part of NODE-5302

      Documentation Requirements

      • Add a note to the migration guides and/or readme of each affected repo
      • DOCSP ticket to document the compat for the upcoming release

      Follow Up Requirements

      • N/A

        There are no Sub-Tasks for this issue.

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            daria.pardue@mongodb.com Daria Pardue
            Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: