Open Morganamilo opened 1 year ago
@sam0x17
I think we need to bump the version of docify
.
After more testing, this issue applies to pallet-fast-unstake
too.
This needs to be updated to use crate-relative paths as outlined in https://github.com/sam0x17/docify/releases/tag/v0.2.0
Master branch already does this https://github.com/paritytech/substrate/blob/6d19bc2d15f96fe513671568ec66e8b21aaed031/frame/fast-unstake/src/lib.rs#L74
Would it be possible to have a cargo publish --dry-run
CI to ensure that all our crates are always in a releseable state?
Would it be possible to have a
cargo publish --dry-run
CI to ensure that all our crates are always in a releseable state?
I think that would be a really good idea
That said, the crate-relative paths thing like above should fail even in a normal build
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
pallet-fast-unstake fails to compile during publish
The macro seems to use some path that changes when
cargo publish
is running the build compared to a normal build.Steps to reproduce
You can't publish the crate normally. As Path deps are used. Use the following
frame/fast-unstake/Cargo.toml
if trying to reproduce:I'm basing this off the last monthly tag. I'm unable to check if this also happens on master as the publish prep has not been ran on that branch.