Update on crates.io

[petreeftime]

There were quite a few changes since version v0.4.0, it would be a good idea to push a new version out to crates.io.

Are there any guidelines for rust-cli organization on how it's best to do this, for example changelog format, steps, etc?

[matthiasbeyer]

So the majority of the rust-cli people use cargo-release. It is not mandatory though. If you want, you can do something else.

Either way, it is strongly recommended that we document how the release process looks like.

---

That said, because our master here is protected and you cannot push to master, I'd say we just use a PR branch (as you did) and release the merge commit as new version by cargo publish && git tag v0.5.0ing it. The repo has AFAICS no tags yet, so I don't mind whether you prefix with v or not 😆 (as long as it is uniform).

[petreeftime]

@matthiasbeyer I don't seem to have ownership on crates.io, so I can't publish. When you have time, go ahead.

[petreeftime]

Release is here: https://github.com/rust-cli/rexpect/releases/tag/v0.5.0

[matthiasbeyer]

Release published.

You don't have access because rust-bus was added to the owners, but not rust-cli, I guess.

Either way, you just got an invite.