I did something stupid and made my crate depend on the git repo for this project like so (I assume) to use code that wasn't yet released in the crate.
I just tried to release a new version of my crate and cargo is telling me that CommandVariant::BuildVersion does not exist when I can see it in the source.
error[E0599]: no variant or associated item named `BuildVersion` found for enum `CommandVariant` in the current scope
--> build.rs:128:29
|
128 | CommandVariant::BuildVersion(v) => Some(v.minos),
| ^^^^^^^^^^^^ variant or associated item not found in `CommandVariant`
This worked Dec 15, 2022 but does not Feb 24, 2023. I was wondering if you had any idea why, I know this is my issue, because I was lazy, but if you have any idea, I'd love to hear it.
Upon further investigation, I rely on commit c81ebdb and that isn't part of a release yet. And apparently crates.io has decided that depending on GitHub is forbidden.
I did something stupid and made my crate depend on the git repo for this project like so (I assume) to use code that wasn't yet released in the crate.
I just tried to release a new version of my crate and cargo is telling me that
CommandVariant::BuildVersion
does not exist when I can see it in the source.This worked Dec 15, 2022 but does not Feb 24, 2023. I was wondering if you had any idea why, I know this is my issue, because I was lazy, but if you have any idea, I'd love to hear it.