node 16

[joshgubler]

No description provided.

[joshgubler]

fixes #22

[stuft2]

Any reason we don't just skip to Node 18?

[joshgubler]

This will be v1.1.2

[GaryGSC]

Thanks for fixing that. ♥

Can we call this v2? The change from node12 to node16 is breaking for anyone using a self-hosted runner with a version that's so old that it doesn't support using: 'node16'. I realize that criteria doesn't apply to BYU, but based on the handful of stars on this repo, I believe we have some external users.

[joshgubler]

Sure. Unfortunately that will be more work to get the security fixes to the end of the row. But that's life.

[GaryGSC]

Yeah. Sometimes it's hard to be good citizens. 🙁

The process would be to:

• Change the base of this PR to target master and update the README's example to reference @v2
• Merge this PR
• Cut a new v2.0.0 release from the tip of master
• Make a new branch, v2, that matches master so that people can reference @v2 and pick up minor/patch updates in the future

[GaryGSC]

(I tend to prefer branches to support the common @v2 use case rather than floating tags.)