The circleci/ruby:2.3-node-browsers image had by default ruby 2.3.6 installed. However, a recent update to this image, upgraded the ruby version to 2.3.7. Our deployment scheme requires the version to be strictly tied into 2.3.6 at the moment, however, this recent update to this image poses a problem to us.
An attempt to update this directly from the config.yml by installing rbenv and ruby2.3.6 fails. Errors with ruby 2.3.6 is specified in Gemfile, but current version of ruby is 2.3.7
There isn’t. Same is true for 2.5.0 now that 2.5.1 got released. It would be great if older tags would be kept around, instead of removing them as soon as a new patch is released…
As far as I know, all image development is done on GitHub. So as a workaround @jdno, you could fork the relevant repo, wind back to the point where the version tag is exposed, build this image, and then pull it in from your own registry.