Local dependencies for publishable crates about cargo HOT 2 CLOSED

Specifying the deps by path in Cargo.toml is the canonical way to do it as far as I know, but it does leave something to be desired in terms of workflow. In my own project that's published to crates.io, what I've been doing is changing them to relative paths while I'm working, and then changing them back and incrementing the versions when I need to publish. It's pretty tedious. :)

I'll put it on my to-do list to add a "publishable" flag and try to come up with a way to automate this, but I'm honestly not super proficient with Rust devops, so I would love some suggestions if anyone has any ideas to share!

Edit to add: Currently the only thing the root-level Cargo.toml does is declare the workspace and its members (kind of like Nx's workspace.json). I'm aware of some projects with pretty sophisticated workspace layouts (e.g. Bevy Engine) with presumably automated build/publish pipelines, so that would probably be a good place to start investigating.

from cargo.