Move createRelease logic to @changesets/cli?

[ianwalter]

It would be nice to be able to use the createRelease logic found here locally, perhaps as a separate release command in the CLI. So that you could do something like:

1. yarn changesets version
2. yarn changesets publish
3. GITHUB_TOKEN=xxx yarn changesets release or yarn changesets release --token xxx

My use case is testing local changes to @changesets/cli but I think it would be good to not have to rely on the GitHub actions, say if GitHub Actions is down but the API is not, or some other reason preventing the action from executing. You could fallback to running the process locally. What do you think?

[Andarist]

At the high-level it seems useful for me - it would allow integrating this part of the workflow into other CIs.

The current implementation of the createRelease is based partially on reading FS information - which makes it less flexible and more error-prone. I think it would be best to avoid such things and if we split this into a separate command we end up again with a state-sharing problem between both commands. OTOH it would be great to have this as a separate command as we'd like to keep things decoupled from each other, keeping responsibilities separated nicely.

Those are just some random thoughts from me right now, I don't know what's the best answer for this just yet.