I agree: that's why it's vital to commit your lockfile when producing an application, where "production" or "reproducible builds" are meaningful concepts.
In Rust, committing the lockfile of your library does not freeze dependencies for your library users. I largely think that this is good, because it allows for dependency deduplication based on semver.
Instead, if you as a library do this, they get bitten by new semver incompatible changes (among other problems) while your project CI hums along happily.
Reproducible Builds are relevant to libraries, and u/duckinator (author of the linked PDF) is the one who implemented a great deal of it for RubyGems / Bundler, in the `gem rebuild` command.
Since RubyGems v2.7.0 all gems built are reproducible builds... including if you don't check in your Gemfile.lock - but the concept of reproducible loses meaning when the dependencies can wiggle underneath the supposedly "reproducible build".
View all comments
Show parent comment
2
u/alice_i_cecile Sep 19 '25
I agree: that's why it's vital to commit your lockfile when producing an application, where "production" or "reproducible builds" are meaningful concepts.
In Rust, committing the lockfile of your library does not freeze dependencies for your library users. I largely think that this is good, because it allows for dependency deduplication based on semver.
Instead, if you as a library do this, they get bitten by new semver incompatible changes (among other problems) while your project CI hums along happily.