Breaking change landed in v9.6.0

[MylesBorins]

nodejs/node#17403 (comment) for reference

TLDR a commit landed that should have arguably been semver major. Should we do another release today or wait until next week?

[gibfahn]

I think the quicker the better. Reverting this is arguably a semver-major change too, so the longer it's out there as latest the worse it is.

Obviously if no-one has the bandwidth to do another release right now then next week hopefully isn't the end of the world.

@watson could you give an idea of how many people you think this might break?

[MylesBorins]

we have a fix open nodejs/node#18944

If CI is green I'll put together a release and get it out tonight

[MylesBorins]

v9.6.1 is out the door