Re-introduce new version script

[cincodenada]

Purpose (TL;DR)

Because of the merge mess with #2426, the version command in package.json was reverted, so that the new version.sh script isn't being used.

Solution

This PR also puts the version.sh script back, and persists a prettier fix in a generated file back to the generation of the file, so it doesn't keep popping up.

How to verify - mandatory

The only way to really, test this is to run npm version, but if #2436 is merged first, then we'll have a way to run that without publishing a release!

Checklist for author

• npm run lint passes
• References to standard library functions are cached.

[codecov]

Codecov Report

Merging #2438 (e36f782) into master (a57bbf6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2438   +/-   ##
=======================================
  Coverage   96.01%   96.01%           
=======================================
  Files          41       41           
  Lines        1906     1906           
=======================================
  Hits         1830     1830           
  Misses         76       76           

Flag	Coverage Δ
unit	96.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a57bbf6...e36f782. Read the comment docs.

[cincodenada]

@fatso83 Okay, I ran through and simulated a clean merge of #2426 to make sure the end-result of all of this merging was the same as if things had gone more smoothly, and this was the only remaining difference I found.

I also snuck in the prettier change, and had a related question - do you have some sort of extra config for changes on your machine, or are you manually deleting the quoted bodies of the changelog, or is there something else going on? My changes command seems to generates a lot more detail in the changelogs than is showing up in your release commits, and I'm curious why!

[fatso83]

@cincodenada Yeah, I manually deleted all I regarded as noise for people browsing the changelog.

[fatso83]

Good call. Was not sure where that came from (not that I was looking 😛 ).