Automating versioning / releasing / publishing libraries in CI

Releasing all the stuff in this repo is quite a bit of work. It involves manually updating package.json and cargo.toml files, which is error-prone. I also need to run npm publish and cargo publish commands in the right order (starting with core libraries).

There is a publish-to-npm action that might prove useful and I'm also using a . Still, this requires manual updating of package.json files.

I'm also using publish-crates, but it's not reliable as it seems to compile atomic-server before atomic-lib, which leads to an error because server depends on lib.

There are some CLI tools that help publishing that I've used in the past:

• cargo release updates cargo.toml + commits + tags
• Some NPM tool... Forgot its name

Start by reviewing the package.json and cargo.toml files and the current release process. Compare the proposed publish-to-npm, publish-crates, and cargo release tools, paying attention to publishing core libraries before atomic-server. Done means CI can version, publish, commit, and tag the libraries reliably without manual ordering or file updates.