-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Restore Cargo.lock with --no-dev-deps #187
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Oh, nah, cargo-hack doesn't restore lockfile in the first place. |
I can confirm the “bug” happens even if my editor is closed, and inside an isolated environment (CI) |
Well, this was originally intentional behavior. To be able to figure out in which lockfile cargo was executed on. That said, my other cargo subcommands (cargo-minimal-versions, cargo-no-dev-deps) restore lockfile by default, so changing the default behavior here would be fine. This should be able to be implemented by just copying a few lines from my other cargo subcommands. |
Implemented in 0.6.0. |
Hey there,
It looks like
cargo hack
does not properly restoreCargo.lock
after running.The text was updated successfully, but these errors were encountered: