Open alvicsam opened 2 years ago
thanks for reporting, @alvicsam .
This is indeed a bit weird, as the owner is already invited, the code is meant to ignore that message and move on, but for some reason, the server tells us it can't invite that owner (as they are already owner) ... Has this been happening a lot for a while already? Otherwise I suspect that might be a hick up on crates.io side...
We are not using cargo-unleash
often so I can't say if it happens a lot but this error happened for the same repo ~2 weeks ago: https://gitlab.parity.io/parity/ss58-registry/-/jobs/1182288
However the very first attempt was successful: https://gitlab.parity.io/parity/ss58-registry/-/jobs/1163787
We use
cargo-unleash
in the ss58-registry repo.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: https://gitlab.parity.io/parity/ss58-registry/-/jobs/1208916
The way how it is used:
Closes https://github.com/paritytech/ss58-registry/issues/40
Closes https://github.com/paritytech/ci_cd/issues/253