Node.js v16 support AKA broadened ranges fix

[balupton]

Broadened ranges are not working correctly, and as such, this is causing packages with edition definitions that only support up to Node.js v14 to fail on Node.js v16.

• Add support to node 16. istextorbinary#200
• fix: Support Node 16 via editions istextorbinary#201

Prior the recent changes of today, this was not being reported correctly, and the logging was too complicated to understand. The recent changes now report it correctly, and will help me identify why the broadened range code is done in such a silly way, so that I can try and understand what is the correct path forward.

• https://github.com/bevry/editions/releases/tag/v6.2.1
• https://github.com/bevry/editions/releases/tag/v6.3.0
• https://github.com/bevry/editions/releases/tag/v6.4.0
• https://github.com/bevry/editions/releases/tag/v6.4.1

Will update this as I go.

❤️ Please consider funding my work so things like this never happen in the first place, or when they do happen, I can afford the time to fix them speedily.

[balupton]

This has been resolved in Editions v6.5.0 and is being pushed out now to all the Bevry packages.

https://github.com/bevry/editions/releases/tag/v6.5.0

Better tests, documentation, and reporting have all been added so that this cannot happen again.

❤️ Please consider funding my work so things like this never happen in the first place, or when they do happen, I can afford the time to fix them speedily.

[balupton]

Seems it is stuck in GitHub Actions limbo:

https://github.com/bevry/editions/actions/runs/1075641317

Not sure how long it will take to get actually get published...