This ensures that the build will use the exact dependencies in Cargo.lock and fail if Cargo.lock has not been updated.
This is a stricter option which will could potentially cause previously working builds to fail, but it is necessary to allow for better reproducibility of builds.
Change-type: major
Release Notes
Rust targets now are tested and built using the --locked flag, to ensure that the cargo lock file is up-to-date. This is meant to improve build reproducibility, but it may cause previous working builds to fail.
This ensures that the build will use the exact dependencies in Cargo.lock and fail if Cargo.lock has not been updated.
This is a stricter option which will could potentially cause previously working builds to fail, but it is necessary to allow for better reproducibility of builds.
Change-type: major
Release Notes
Rust targets now are tested and built using the
--lockedflag, to ensure that the cargo lock file is up-to-date. This is meant to improve build reproducibility, but it may cause previous working builds to fail.