You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's unclear at this time when we should drop support for a particular Node version. It's also unclear what our guidance should be for running against smaller matrices. Cosmos' current configuration, for example, won't catch breaking changes in the latest Node version.
I'm not sure why Cosmos only runs against Node 8. No issue from our side running the full matrix.
As much as I would like to drop Node 8 support in v4, our telemetry suggests that may not be wise. Talked with @bterlson this last week. Happy to share more over teams.
Today we have a guideline stating we must support all LTS versions of node.
(It's a little out of date, so I have a PR to fix that. )
We currently run most CI against a wide matrix from 8 to 14:
https://github.com/Azure/azure-sdk-for-js/blob/master/eng/pipelines/templates/jobs/archetype-sdk-client.yml
There are some irregularities we should think about:
It's unclear at this time when we should drop support for a particular Node version. It's also unclear what our guidance should be for running against smaller matrices. Cosmos' current configuration, for example, won't catch breaking changes in the latest Node version.
/cc @ramya-rao-a @bterlson @southpolesteve for thoughts.
The text was updated successfully, but these errors were encountered: