deps: increase "engines" to "node" : "^12.22 || ^14.13 || >=16"

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.

[wraithgar]

Makes npm warn users if they are using an unsupported Node version.

Checklist

• npm install && npm test passes
• commit message follows commit guidelines

Description of change

Commit message follows the pattern from the last time this field was updated: #2153

[richardlau]

I think we usually treat dropping support for a version (in this case Node.js 10) as semver-major.

[wraithgar]

That was my first instinct but then I checked the git history on that line and that was not done last time. In the cli we are treating this kind of change as a semver major, and would happily amend my commit.

The current testing matrix only includes 12.x, 14.x and 16.x which I believe only uses the latest versions in those lines.

[richardlau]

I don't feel strongly enough about this to argue either way so I'll remove the label -- this specific change is is advisory (at least for npm, I think some (all?) versions of yarn enforced engines by default).

Given that we don't actively test against Node.js 10 we can't even say that we aren't already broken there (albeit I'm sure we'd have received plenty of reports if that been the case).

If other node-gyp maintainers disagree, feel free to put back the semver-major label.

[rvagg]

let's do semver-major !, it's not a big deal to bump that, releases are relatively cheap and signalling is important

@wraithgar do you have any urgency about getting a release for this out for consumption upstream?

[wraithgar]

@rvagg I'd say medium low urgency? It's mostly about allowing node-gyp to stay current w/ the latest make-fetch-happen. v10 has a couple of bug fixes in it, nothing very big (yet). It would also shrink the npm cli bundle size a bit by allowing us to dedupe make-fetch-happen up out of node-gyp.