-
Notifications
You must be signed in to change notification settings - Fork 67
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
Building without lockfile fails #175
Comments
@jmcconnell26 Can you take a look at this? 🙏😃 |
@anderejd, I've landed #178 which should fix the immediate issue. |
Long term I wonder if it might be possible to implement some sort of Canary CI/CD pipeline which attempts builds without lockfiles, to detect stuff like this, and give us at least some visibility into issues like this? |
Sounds like a good idea. Should be fairly simple to add a second build to the CI scripts/configs. |
Raised #183 to perform a build without the lockfile, which should let us catch this in future. |
Closing this as this was resolved - for the sake of completeness I've been using this as well :) Re-open if replicated. |
It looks like
cargo-geiger
is relying on internal details ofcargo_metadata::Dependency::target
that have changed in v0.12.2.The text was updated successfully, but these errors were encountered: