Original forum topic: https://forum.snapcraft.io/t/does-snapcrafts-rust-plugin-respect-the-cargo-lock-file/14776?u=zicklag. I have a Rust project that is getting built with build.snapcraft.io service and I noticed that the automated builds are not respecting the `Cargo.lock` file that is included in my project's source. Instead, the snapcraft build is acting if the lock file was not there and using the latest updated versions of all of the crates declared in my `Cargo.toml` file. This causes problems because an updated dependency is getting used that causes the project not to compile. Granted, the fact that an updated dependency can cause a compile to fail on my project likely indicates that a crate I'm depending on is not correctly following semantic versioning, but regardless, the fact that snapcraft is not respecting the lock file could result in even harder to notice bugs because the snapcraft builds are going to be different than the builds made without snapcraft. For an example of the failure: build.snapcraft.io build log ( which failed ): https://build.snapcraft.io/user/katharostech/lucky/772273 my CI build log ( which succeeded ): https://cloud.drone.io/katharostech/lucky/259/1/2 The commit of my project: https://github.com/katharostech/lucky/tree/9079bbcb46bb8df4ed73c9a10f5eb6dc8f92772f