We are using the circleci/ruby docker base, specifically the 2.5 tag. This means that if there is a sub version change (as there was here, .7 to .8) the CI will fail. I think the failure is suitable to alert us about the base update, and that way we don't hard code a version into the CI that possibly needs a security fix, etc. If this build is successful then that is sufficient for this to merge.
We are using the circleci/ruby docker base, specifically the 2.5 tag. This means that if there is a sub version change (as there was here, .7 to .8) the CI will fail. I think the failure is suitable to alert us about the base update, and that way we don't hard code a version into the CI that possibly needs a security fix, etc. If this build is successful then that is sufficient for this to merge.
Signed-off-by: vsoch vsochat@stanford.edu