cargo-unleash

cargo-unleash copied to clipboard

The package is published but returns "failed to invite owners to crate" error

2

We use `cargo-unleash` in the [ss58-registry repo](https://github.com/paritytech/ss58-registry). As I can see it successfully publishes crate to crate.io (for example: https://crates.io/crates/ss58-registry/1.4.0) But in the same time it returns error during publishing:...

alvicsam

The current impl of the cycle detection is mildly overzealous, and also reports dev-depencies as cycles which (iiuc) ought to be removed. ``` [package] name = "foo" version = "0.1.0"...

drahnr

add `cargofmt` to clean up cargo.toml files

1

When editing cargo.toml files a few things happen that make the result a little unclean: - when updating the version, we sometimes have to add it and that leads to...

gnunicorn

When checking the metadata we should also check that the file defined in the `readme`-Metadata exists.

gnunicorn

To prevent dependency-cycles multiple commands currently by default remove dev-dependencies from the `Cargo.toml`-files first. While neat, the UX is still lacking because: - if you change specific files an then...

gnunicorn

We know the number of crates we are releasing and we _intentionally_ wait between releases (which takes up most of the time after checking), so we should be able to...

gnunicorn

Xanewok

fixes #24 Todo: - [x] only change if different - [x] track the ones changed, keep a `Cargo.toml.bak` for later - [x] provide command to revert them - [x] revert...

gnunicorn

refs #15 .

gnunicorn