That worked, thanks! Seems like crates.io only verifies crate existence, not version match. If anyone maintaining crates.io sees this, please don't patch this loophole, this is what --no-verify was made for imo 
.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Publishing crates from the same workspace | 6 | 1721 | June 24, 2017 | |
| How to release related crates with fake (dev-dependency) cycle? | 5 | 697 | February 20, 2019 | |
| Cannot publish library because of local unpublished crate | 2 | 520 | January 29, 2024 | |
|
Cargo - Publish crate from workspace where a newer version of another crate depends on that version
|
6 | 407 | November 14, 2025 | |
| Cannot publish crate within workspace | 4 | 692 | February 26, 2020 |