You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are realizing that during the release of a new version of a crate, we need to do some checks, such as checking that all codeowners are also on crates.io [see https://github.com/rust-vmm/rust-vmm-ci/issues/142], run cargo-semver-checks [see https://github.com/rust-vmm/rust-vmm-ci/issues/135], etc.
The best thing then might be to provide a single script where we do all the checks and if everything passes, proceed with the release.
As for semver checks, since there are a lot of inter-dependencies in the rust-vmm ecosystem, maybe we can check that all crates build with new (minor) versions?
We are realizing that during the release of a new version of a crate, we need to do some checks, such as checking that all codeowners are also on crates.io [see https://github.com/rust-vmm/rust-vmm-ci/issues/142], run
cargo-semver-checks
[see https://github.com/rust-vmm/rust-vmm-ci/issues/135], etc.The best thing then might be to provide a single script where we do all the checks and if everything passes, proceed with the release.
cargo-semver-checks
rust-vmm-ci#135The text was updated successfully, but these errors were encountered: