Package supports Node >= 12 but CI only tests Node 20 and 26

[Fdawgs]

As title states, engines.node in package.json is ">=12.0.0" but the CI only tests Node 20 and 26.

Bug fixes and new features could accidentally break functionality when using an older Node version, with no CI feedback.
Either the test matrix in the CI workflow needs updating with old LTS versions (12, 14, 16, 18), or the engine version needs bumping (which would be a breaking change).

[spencermountain]

Thanks frazer - i really need the help with this fast-changing npm ci stuff, and your work here is really helpful. i never wanna make hackernews for some config i did (or didnt) set.

I do have a question abt this one- someone with a weird art-project on an arduino running node 12, does that mean their project would stop working with this change? I know these node versions are eol, but i dont want to hurt projects that are dangling around.
I think some of the reasons node <12 wouldnt run are build-processes, and not end-user use cases. people who are tagging tweets should be fine on any node version, i reckon.
any thoughts? i may be wrong.
cheers