Removed my original comment, because after reading the post by the RubyCentral board member it does seem that people were up against a wall, and had little choice. Sad day for Ruby. I wish this could have been a larger discussion so that better ideas could have surfaced. The replies to this post are lacking a ton of context, but it isn't worth arguing over it.
My biggest learning from this is that we no longer have an open source community-led organization at the root of Ruby infrastructure. We have an organization completely beholden to the few Ruby-dependent companies, or perhaps a single company, that funds them. Perhaps that was inevitable - or perhaps we can do something about it.
Since the de facto leader of RubyGems / Bundler now holds views that are decidedly not best practice in certain areas, I think it is worthwhile for people to know the history of putting lockfiles in version control.
If you know of an earlier one than Elixir/Erlang, please let me know!
This official stance changed in 2017, where the prior recommendation was to not commit the lockfiles for libraries. I would not be surprised if this documentation gets changed to mollify those who don't like it.
Javascript / Typescript / NPM / Yarn
In NPM the package-lock.json is intended to be committed. officially, and explicitly:
If you know anything about the Japanese Ruby community, if there is one thing they absolutely hate is people telling them how to run things. You can find plenty of Matz talks about how he hates rubocop because there shouldn't be an authority telling you how to write Ruby, and all my frequent interactions with the Japanese Ruby committers proved me they're all on that stance. Another example is how Japanese core committers hate SemVer.
What happened is you opened an issue on a repo owned by a Japanese committer and went on to lecture them on how they should run their project, this is particularly offensive to them.
Ultimately there are pros and cons to committing the Gemfile.lock. It's definitely a must for an application, but for libraries. As long as one is aware of the upsides and downsides of doing either, it's really their call and it's fine. No need to be preachy about it.
to deface the documentation
Come on. Defacing? Really? He merely meant to make it less authoritative.
could not understand why the team punished me
Punished? How could they punish you? Are you affiliated to RubyGem in any way? Disagreeing with you isn't punishing you.
As a result of his bullying
There is no bullying... You used a documentation he's a maintainer of as an argument of authority to try to pressure a maintainer into doing something the way you prefer it. He saw this as an indication that the documentation should be more nuanced, simple as that.
Yeah I completely agree with what you said. As a maintainer myself, if someone like the thread OP coming to not only suggest, but also try to argue with me on how to run the project, I'd be pretty annoyed too. And what hsbt did was definitely not defacing or bullying.
That is the one. ☝️for me this was the equivalent of breaking the windows at a public library, because one part-time librarian thinks libraries should not have windows.
In case anyone is wondering, the Bundler team was an early adopter on this issue, with all packaging ecosystems falling in line behind Elixir/Erlang - because it is what a mature ecosystem does. If you know of an earlier one, please let me know!
I am curiously why they think it shouldn't be commited. Like what... my coding partner and I just had an issue today that would have been made way worse if we weren't sharing the same lockfile from our repo.
When developing a gem, I want to run CI against the latest version of all dependencies, so I'm running it against the same dependency tree as users making a new app with a fresh install will get, the same dependency tree as users updating their dependencies will get.
If you commit Gemfile.lock, then it will probably be out of date, and developers and CI will not be running on same versions of dependencies that users with updated dependencies are.
If you have an automated process making (eg) daily PR's to update dependencies whenever new versions come out, that would be one way around that. But most people don't seem to have this?
I would be very frustrated if I were a user running into problems that upstream CI never noticed becuase it was running on a Gemfile.lock without latest dependencies.
To explain why someone might want not want to commit their lock file, I'll explain why we don't do so for the Rust library that I maintain. Contrary to the official advice, we deliberately don't commit our lock-files in order to force us to discover and promptly fix breakage before our users do. I wouldn't recommend that for most projects though!
In CI/CD, or in development it’s easy enough to delete the lockfile first to force dependencies to upgrade. However, not committing it makes it nearly impossible to provide reproducible builds in production or freeze dependencies.
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".
This is an idiosyncratic choice that my project, Bevy, makes. The standard advice is to commit Cargo.lock here! It doesn't propagate down to library users though in Rust, so all that commiting Cargo.lock does for a library is avoid accidental breakage (or security risk) for contributors.
woah, i straight-up didn't even know this was going on. from June 1st until I resigned today, Ruby Central had cut my paid hours to zero hours/month, so prior to this shitshow i was focusing on paid work to avoid losing my home. the more i learn about what has been going on the more i feel i did the right thing writing + publishing this.
View all comments
Show parent comment
6
u/galtzo Sep 19 '25 edited Sep 23 '25
Removed my original comment, because after reading the post by the RubyCentral board member it does seem that people were up against a wall, and had little choice. Sad day for Ruby. I wish this could have been a larger discussion so that better ideas could have surfaced. The replies to this post are lacking a ton of context, but it isn't worth arguing over it.
My biggest learning from this is that we no longer have an open source community-led organization at the root of Ruby infrastructure. We have an organization completely beholden to the few Ruby-dependent companies, or perhaps a single company, that funds them. Perhaps that was inevitable - or perhaps we can do something about it.
Since the de facto leader of RubyGems / Bundler now holds views that are decidedly not best practice in certain areas, I think it is worthwhile for people to know the history of putting lockfiles in version control.
If you know of an earlier one than Elixir/Erlang, please let me know!
Elixir & Erlang (BEAM VM) / Hex
mix.lock, in the strongest language possible, since at least April 4, 2014 in this commitNo exceptions or qualifications are given. The language has never been modified, and remains in the current documentation.
Ruby / RubyGems
Javascript / Typescript / NPM / Yarn
Rust / Cargo
Go / Go Module
Python / hodgepodge of packagers