tools: update GitHub Actions workflows

[VoltrexKeyva]

Thanks for contributing!

• Have you updated CHANGELOG.md?

[VoltrexKeyva]

This also fixes a typo in the changelog.

[zbjornson]

Do you have a specific motivation for wanting to drop older versions of Node.js? Right now it's not adding to our maintenance burden, and folks have complained when we stopped providing prebuilds for EOL versions, so we've continued to test them in CI.

[zbjornson]

This file isn't used in this branch.

[VoltrexKeyva]

Then is there a reason it exists in this branch? Should we remove it?

[VoltrexKeyva]

Do you have a specific motivation for wanting to drop older versions of Node.js? Right now it's not adding to our maintenance burden, and folks have complained when we stopped providing prebuilds for EOL versions, so we've continued to test them in CI.

My main motivation for that is to be able to update dependencies without having to worry about it breaking support for older Node.js versions since most of them are removing support for versions like v10 and v12, as well as being able to use newer features not available in older versions that are more convenient to use and offer better performance (such as the nullish coalescing operator (??) and others), since most users use the newer versions rather than the older ones nowadays, but I would understand if you folks still want to support older versions.

[LinusU]

I personally think that we shouldn't rush to release a new major version since it creates extra churn for the consumers of this package. We only have three dependencies right now, and only one of them has a newer version available, simple-get, and there is nothing in the new version that would benefit us at this time...

[VoltrexKeyva]

Fair enough, I'll revert the changes that removes the old Node.js versions from the testing matrix.

[LinusU]

LGTM 👍

The only thing I'm not 100% sure about is the check-latest: true, not sure that it's worth busting the cache more often just to always be on the latest version. In fact, I'm not sure that it's nice to automatically be on the latest version because of the same reasons discussed before, even if breakage from newer Node.js versions should be very rare...

[VoltrexKeyva]

@LinusU the main reason I think getting the latest version is better is because if we use the cached one, a scenario can occur where it lands on a Node.js version with regressions and/or critical issues and keeps using that, however always getting the latest version should avoid this problem as such issues in the runtime generally get fixed pretty quickly.

I also encountered this problem myself which was very annoying to deal with.