Auro Node support

This document is designed to illustrate and communicate Auro's commitment to security and the safety of our users by supporting the latest development environments and dependencies whenever and wherever possible.

The Auro team is committed to an overlapping support model for Node.js. This means that each repo should be able to be used within the current Active LTS as well as the previous version that is in maintenance. Keeping in mind, these are recommended versions and not a strict specification.

Lit element Node support

Additionally for general consumption of Auro tech, the version of Node your app should support is based on direct dependencies. For Lit Element, documentation states "Node 10 or greater" (as of Q4 2023). That said, repositories state supporting latest -2 for development and testing. We feel that this will be a consistent trend. For our purposes we are choosing not to support a version of Node that has exceeded its End of Life date.

How we maintain versions

The following illustrates how this would appear in the ./package.json file as Auro is not directly supporting any odd-numbered releases.

"engines": {
  "node": "^18 || ^20"
}

Auro's repository testing matrix will consider the following:

node-version: [18.x, 20.x]

The release will directly support the current LTS:

node-version: 20.x

Repo `settings.yml`` file will reference:

contexts: ["test (18.x)", "test (20.x)", "license/cla"]

Following the Node.js Release Working Group release schedule Auro commits to maintaining a similar schedule of support whereas by the 1st quarter of the year we will begin migration to the next LTS which is expected to be completed by the 4th quarter of the same year.