Use Case

We always test on all Node versions, but only build and publish prebuilds on our lowest LTS Node version. Prior to upgrading to Node20+, we built prebuilds on Node16 and ubuntu bionic, with a glibc version of 2.27. After upgrading to Node20+, we switch prebuilds from ubuntu bionic to ubuntu noble. Ubuntu noble has a glibc version of 2.39, which meant our prebuilds in the 7.0.0-alpha release were incompatible with any versions of linux that have a lower glibc version.

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward