Use Case

As a Node.js user and driver developer
I want the latest LTS to be tested.
So that we're sure the latest version works as expected.

User Impact

• All Node.js users that use the LTS release branch.

Dependencies

• nvm, Node.js

Unknowns

• None

Acceptance Criteria

• We should add Node.js 16 & 17 to our testing matrices for all our supported libraries.
• We should consider adding the "latest" LTS version as well. In general the latest version is acceptably stable and it would be good to learn of any issues sooner than later.

Implementation Requirements

• Update NVM version, take a look at how NVM is managed in the main branch. There's a single script that handles the installation and sourcing of shims/environment variables. Consider bringing this script to each CI we're making this update to.
• Add Node.js version detection logic for newer versions of Node. You'll find in the driver we have a script that translates node version number to node version name.
• Enable Node.js 16  & 17 testing in PRs.

Testing Requirements

• None

Documentation Requirements

• File this ticket as Documentation changes needed, to add to the compatibility table on our docs page.

Follow Up Requirements

• None.