I think 8.0.0 shipped along with its website updates just in time. Both that and a new version of ffi (1.17.0) no longer installable on the older Ruby setup we were using in Netlify were released on June 2, probably mere hours apart.
This has told me that, just maybe, we should be using the Gemfile.lock. Since I can get the same Ruby version installed on Netlify as in my development environment on Gitpod, we might as well match everything up.
Long-term, though, I think this will end up being motivation to move the rest of the site into Sphinx. It's a pain managing multiple build toolchains, especially given how outdated Netlify's build images are; they still offer only a deprecated Xenial (16.04) based image, and a long-in-the-tooth Focal (20.04) image. Their relevant docs don't even say anything about installing additional Python versions other than the preinstalled 2.7 and 3.8.
I think 8.0.0 shipped along with its website updates just in time. Both that and a new version of
ffi(1.17.0) no longer installable on the older Ruby setup we were using in Netlify were released on June 2, probably mere hours apart.This has told me that, just maybe, we should be using the
Gemfile.lock. Since I can get the same Ruby version installed on Netlify as in my development environment on Gitpod, we might as well match everything up.Long-term, though, I think this will end up being motivation to move the rest of the site into Sphinx. It's a pain managing multiple build toolchains, especially given how outdated Netlify's build images are; they still offer only a deprecated Xenial (16.04) based image, and a long-in-the-tooth Focal (20.04) image. Their relevant docs don't even say anything about installing additional Python versions other than the preinstalled 2.7 and 3.8.