Missing npm 10.x & 11.x tests

[MikeMcC399]

Issue

The currently active versions of npm 10.x and 11.x are not tested in tests/main.test.ts.

Corepack

Corepack tests/main.test.ts uses:

• npm@6.14.2

corepack/tests/main.test.ts

Lines 129 to 131 in a7cb9f6

	[`npm`, `6.14.2`],
	[`npm`, `6.14.2+sha1.f057d35cd4792c4c511bb1fa332edb43143d07b0`],
	[`npm`, `6.14.2+sha224.50512c1eb404900ee78586faa6d756b8d867ff46a328e6fb4cdf3a87`],

npm

• npm CLI commands documentation includes the current 11.x version and lists legacy versions 6.x - 10.x
• npm/cli/releases shows npm@11.1.0 as current latest release (npm view npm version).
• npm Support Policy restricts backporting security updates to versions shipping with maintained Node.js versions. These are listed on https://nodejs.org/en/about/previous-releases and currently correspond to npm 10.x.

Suggestion

Update tests/main.test.ts.

Consider adding legacy versions (corresponds to next-x tags):

• npm@7.24.2
• npm@8.19.4
• npm@9.9.4

Add currently supported versions:

• npm@10.9.2
• npm@11.1.0

[aduh95]

We do test with the latest version, I don't see the point for testing other versions but I guess I'm not opposed to it

[MikeMcC399]

@aduh95

We do test with the latest version, I don't see the point for testing other versions but I guess I'm not opposed to it

• Based on the realization that all versions of npm prior to npm@11.1.0 were signed with the same keyid (see Saveguards for keyid mismatch #616 (comment)) I also now don't see the advantage of testing additional versions. The proposed tests would only reveal the availability of the different versions. They would not exercise any different code in Corepack.
• Withdrawing this suggestion therefore.