Autogenerate version file artifact

[StoneCypher]

Offer to autogenerate was accepted

Plan is:

1. npm script which removes the old one
2. npm script which creates the new one
3. npm script which updates the README.md
4. all to be lodged in the standard build process before the build proper begins

[hildjj]

Hm. I want to think about the release process also. Right now, i have something hand-rolled and kind of awful in tools/release.

[StoneCypher]

This is what it looks like in practice.

• npm script invokes js with node
• build js is trivially simple, standard js, and portable

[hildjj]

That's about exactly what tools/release is doing now.

[StoneCypher]

Then I apologize, but I don't understand how it got out of date previously.

Does it just need to be made part of the build?

[hildjj]

Yes, that's all. Either someone was updating it by hand (shudder), or I only got part of two different repos that were munged together and had some tooling misplaced (likely).

I'm still open to have a better release process. semantic-release seems like massive overkill.

[StoneCypher]

ya this seems a bit much

i think just auto-tagging, auto-releasing, and auto-pushing-to-npm after a successful test, using gh actions, is probably good enough. what about you?

[hildjj]

Send particular comments on tools/release which is based on what @phpnode and i did on the 1.0.0 release. We can remove, add, or replace things there.