Open blumamir opened 4 months ago
That last 7.x release was: '7.6.17': '2021-05-18T08:43:02.672Z',
So perhaps its test-all-versions (TAV) config could be limited to just the latest "7.6.17".
The last 8.x release was: '8.4.7': '2022-06-14T07:25:26.179Z',
So, perhaps limit this as well to just the latest.
The last 9.x was: '9.4.3': '2023-06-12T10:25:05.603Z',
Again, perhaps limit to just testing the latest 9.x.
Then perhaps add a range of 10.x releases.
Now that we are on test-all-versions@6.1.0 we could use use the versions mode
feature (https://github.com/watson/test-all-versions?tab=readme-ov-file#advanced-versions-usage) to limit to just testing a few. E.g. something like:
versions:
include: ^10.0.0
mode: max-5
Hi @trentm ,
Can you please assign this issue to me? I'm new to opensource and would like to help.
@amkarn258 Done. Thanks for taking a look!
The @nestjs/core instrumentation defines an open range for supported versions
>=4.0.0
, which is capped in #2196 to the latest current major version.However, since the instrumentation was last updated, the package released few more major versions, which the instrumentation will attempt to patch, are not part of the current
.tav.yaml
rangeThis issue is to add those versions to the test-all-versions yaml, make sure instrumentation works for these versions (exaime any potential changes to the functions we patch with new versions) and consider upgrading the version in
devDependencies
.