Does Tokio have any release flows they can share

[nhtyy]

As i'm maintaining larger crates with many contributors, im curious how tokio manages releases.

For me, Ive ran into plenty of issues that seemingly could only be reproduced after publishing to crates-io, which is really bad. As well, cargo package is not really in a great state, ie, if you make changes across crates in a workspace, cargo package will try to read from crates io.

So just curios, any best practices or recommendations on how Tokio manages to pull off flawless releases?

[Darksonn]

We do sometimes make mistakes when releasing, but we try to avoid making the same mistake more than once. Often you can use a CI job to catch the problem in the future. For example, we run cargo-semver-checks, we build the crate with the MSRV rustc, we build the crate using -Zminimal-versions, we build the docs with the same flags as docs.rs, we run the tests of certain downstream dependencies (hyper and quinn), we run check-external-types. You can remove path = "../dep" on cross-workspace dependencies to build with the version on crates.io rather than whatever you have locally.

You can read our CI jobs here.