🐛 Summary
I open a new issue because I don't have permission to reopen #67
Deleting the Cargo.lock file is not a solution to the problem. This file is needed for reproducible builds. Please add it back.
My point was in release 1.5.1 you forgot to update it, I never asked for it to be deleted.
Please, maybe consider adding a build workflow to your CI that uses cargo fetch --locked and cargo build --frozen --release so this is easy to detect automatically.
To reproduce
Steps to reproduce the behavior:
- Clone repo
- Checkout latest release
- Ty to build
Expected behavior
I should be able to build and get the same (bit-by-bit) identical binary as the one you provide.
What did you expect to happen that didn't?
It does not build because Cargo.lock is now missing.
🐛 Summary
I open a new issue because I don't have permission to reopen #67
Deleting the
Cargo.lockfile is not a solution to the problem. This file is needed for reproducible builds. Please add it back.My point was in release 1.5.1 you forgot to update it, I never asked for it to be deleted.
Please, maybe consider adding a build workflow to your CI that uses
cargo fetch --lockedandcargo build --frozen --releaseso this is easy to detect automatically.To reproduce
Steps to reproduce the behavior:
Expected behavior
I should be able to build and get the same (bit-by-bit) identical binary as the one you provide.
What did you expect to happen that didn't?
It does not build because
Cargo.lockis now missing.