cargo-semver-checks Crash Report (after using absolute path to dependency, panic: "we declared a dependency on a crate that doesn't exist in the metadata") about cargo-semver-checks HOT 1 CLOSED

I believe this is the same cause as #453 and a few other recent issues.

The failure is right after the line:

Parsing arti-bench v0.8.5 (current)

and that crate is a bin crate, with no lib target. By default, since semver-checking was started inside a workspace and not inside a particular crate's directory, cargo-semver-checks checks everything in the workspace. That binary crate should have been skipped automatically since there's no library API to check in it, but due to a bug it's being checked anyway and the check trips that assertion.

Sorry about that. I've been a bit swamped lately and haven't gotten a chance to work on this at all recently. If you happen to have the interest and cycles, I'd appreciate help and would be happy to point you in the right direction!

If not, no worries! You should be able to work around this for now in a few ways: by passing --exclude arti-bench, passing -p <crate-to-check> explicitly, or by doing a cd into a specific crate's directory and checking from there.

from cargo-semver-checks.