|1.0.8||Aug 5, 2023|
|1.0.7||Jul 4, 2023|
|1.0.6||Dec 17, 2022|
|1.0.5||Sep 28, 2022|
|1.0.4||Jul 1, 2022|
#258 in Cargo plugins
158 downloads per month
New Cargo versions sometimes write out a lockfile that triggers parse failures in old Cargo versions.
$ cargo +1.41.0 check ... Finished dev [unoptimized + debuginfo] target(s) in 0.91s $ cargo +1.37.0 check error: failed to parse lock file at: /git/testing/Cargo.lock Caused by: invalid serialized PackageId for key `package.dependencies`
cargo unlock subcommand simply deletes the offending lockfile so that the
old Cargo can proceed. Install by running
cargo install cargo-unlock.
cargo unlock has three advantages:
It still works if run from a workspace member, where the lockfile would be located at the workspace root rather than the current directory.
It works if run from a subdirectory of a crate rather than the crate root.
If like me you use
export FIGNORE=argo.lockin your shell so that all autocompletes prefer Cargo.toml over Cargo.lock, this is easier to type.
LicenseLicensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.