chore: add min version in TAV matrix

[david-luna]

Tweak tav.json file and tav.yml and tav-command.yml actions so we can specify which is the min version where the module should be tested. The matrix generated contains only one row where each element contains module node_version in a single place.

set to draft to test it and discuss with the team

Checklist

• Implement code
• Add tests
• Update TypeScript typings
• Update documentation
• Add CHANGELOG.asciidoc entry
• Commit message follows commit guidelines

[david-luna]

/test tav

[david-luna]

/test tav

[david-luna]

The matrix workflow shows the values of each dimension for each run. In our case dimensions are

• nodeAndVersion: which contains the string to use in the TAV command (eg. hapi 16)
• count: the total number of elements in the matrix

When looking at the workflow, the list of runs differs a little bit of what we are used to

[david-luna]

/test tav fastify

[david-luna]

/test tav fastify 20

[david-luna]

/test tav fastify 10

[david-luna]

/test tav fastify 10

this did not run anything since min node version set is higher than 10

[david-luna]

/test tav unknown

[david-luna]

/test tav unknown

[david-luna]

/test tav unknown

this fails because the package name is not in listed in tav.json

[david-luna]

/test tav

[david-luna]

Note for reviewer: to run less tests we add minVersion to 18. This shall be updated with the proper versions if the PR is okay to merge

[david-luna]

/test tav express

[david-luna]

/test tav express,fastify 20

[david-luna]

Turns out you can pass a single array (so it's a 1 dimension matrix). Now the list of the tasks looks nicer showing.the module name and the node version separated by a space.

[david-luna]

/test tav express,nonExistingPackage,fastify

[david-luna]

/test tav express,nonExistingPackage,fastify

Now it fails and logs the name of the wrong package

[david-luna]

/test tav

[david-luna]

/test tav

[trentm]

LGTM. A couple of nits is all.

[trentm]

Hrm, I guess with all these minVersion: 8s, it means there won't be a large reduction in the number of jobs. Still probably worth keeping.

(Not part of this PR, but I wonder if we could consider dropping testing for versions of these packages that are, say, older than 2y and not of the latest major version. That might enable raising the minVersion here.)

[david-luna]

Maybe we can leverage the multiple package option we have, here we are testing 2 packages in the same job

{"name": "bluebird,got", "minVersion": 8 }

This is actually what I want to do for @aws-sdk/client-* to test all of them at once for each version. There might be other groups we could make perhaps @opentelemetry/* or mysql? Of course some test review is needed to see compatibility. Also I think the runTestFixtures util introduced in the ESM support PR would come handy

we could consider dropping testing for versions of these packages that are, say, older than 2y
I agree and also I think it could be something to motivate users to update

[david-luna]

/test tav fastify 20