Autogenerate version file artifact about peggy HOT 7 CLOSED

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

from peggy.

This is what it looks like in practice.

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

from peggy.

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

from peggy.

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?

from peggy.

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.

from peggy.

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?

from peggy.

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.

from peggy.