-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected failed to select a version for the requirement
for workspace cargo release publish
#705
Comments
The problem is we are trying to get |
Hi! Thank you for the reply :-) However, I'm a bit confused. Reading your reply (specifically the |
I'm saying that what we do is very limited by what We could also more thoroughly fix this but the work but into that would best instead be done in cargo instead, hence the issue. |
We're considering switching to cargo-release to perform the publish part of our two-stage release process.
I just ran a dry-run
cargo release publish
locally on a branch with this change checked out:heroku/libcnb.rs#690
And got this error:
What seems strange to me (and potentially a cargo-release bug), is that the crate in question (
libcnb-data
v0.15.0) is already "dry run published" earlier in the command output - so the0.15.0
version should have been found whilst processinglibcnb-cargo
?Also, several other of the crates that succeeded during the dry-run also depend upon
libcnb-data
, but they did not fail. Thelibcnb-cargo
crate is a binary crate, so could that be the difference?As far as I know, there are no circular dependencies.
I tried using
--no-verify
but that didn't help either.This was using:
The text was updated successfully, but these errors were encountered: