Deprecation warnings thrown in CI

[kurtmckee]

A new version needs to be released to support Node 16. The code appears to be in place already, so all that seems to be needed is a new version.

Other projects are seeing warnings in CI caused by the v1 tag still requiring Node 12, which is no longer available. Here's a recent example from codespell's CI.

I don't have a recommendation whether this should be a new v1 or should jump to v2, but a new version is needed.

[DimitriPapadopoulos]

[DimitriPapadopoulos]

• GitHub Actions: All Actions will run on Node16 instead of Node12

[DimitriPapadopoulos]

I'll bump from node16 to node20 before trying to prepare a v2, so that it lasts longer.

[kurtmckee]

Friendly ping. 😀

[DimitriPapadopoulos]

@kurtmckee The version has been bumped from node16 to node20 in #5, and is part of v1.2.0. What would be missing?

[kurtmckee]

Ah, I had thought that this was only to be released with v2 based on the above discussion.

Only thing missing is for me to close this issue! 😀 🥳