Failure when using workspace with package renaming

[Roms1383]

Hi and thanks for this crate I've been using it for years and always enjoyed its simplicity.

This morning I refactored one of my project to split the monolith into a workspace with types and cli for future reusability.

I renamed types into inkanim-types and use it as a dependency for cli (which is the main crate so it's officially called inkanim).

To avoid having to rename all the imports I specified it this way in the cli crate:

[dependencies]
inkanim = { path = "../types", features = ["clap"], package = "inkanim-types" }

Only quirk, now katyo/publish-crates@v2 does not recognize it as a workspace member, while it actually is:

Thanks in advance for taking the time to read me.

[Roms1383]

after losing my whole morning on this (and polluting my commits history like crazy), I realized part of the mistake on my side is that cargo refuses to publish a dependency which relies on an unpublished internal dependency.
so essentially i split inkanim into both inkanim-types (that i don't intended to publish initially) and inkanim (a.k.a inkanim-cli, but i kept the name as it allows using the same CLI commands without breaking developer experience).
in the end i ended up publishing inkanim-types on crates.io, and everything went back to normal.

that being said this PR might still be relevant as i ran publish-crates locally and it fixes confusion in package.dependencies iirc.