Hi CircleCI Community,
We use the
ruby:2.4.6-node-browsers tagged docker images in our build. Recently, it appears that this docker image had its default version of rubygems updated to 3.x.
I’ve been looking and I can’t find an announcement that this breaking change (the
--no-ri flags were removed in favor of
--no-document) would be occurring. Seeing as RubyGems 3.0 was only released in December it doesn’t seem like this has been a long time coming.
It also breaks my expectation that without any code changes on my part a new run of my build might change because a tagged docker image was updated transparently to me.
I understand and value the effort the CircleCI team puts into maintaining these docker images, but it would be my expectation that transparent updates to them would not contain major version updates with breaking changes by default.
In the mean time we’ve updated our build scripts to support the new RubyGems syntax and everything is fine.
I understand that many people also want and need the new versions of various dependencies that are included in the image. I wonder what solution the community would prefer to solve the needs of people who need stable major versions, and also the needs of folks who need updates to these dependencies. In some cases I have built my own dockerfiles that install updates to browser dependencies but not everybody may be interested in owning their own images just for CI.