I struggled with this issue when I realized that it was too much work to update my blog to use the latest version of Hugo. I wasn't able to run the old hugo binary on my new version of MacOS (segfault). And I couldn't even compile the old code from source, because I couldn't get older versions of Go to work. Some of the old Go dependencies had even been renamed or deleted.
Eventually I realized that I could continue using my old version of Hugo forever (0.21) if I run it in a Linux Docker container. The output is still static HTML and CSS, and all the static files are cached and served with a CDN (CloudFlare), so I'm not particularly worried about security updates.
I'm not sure how long this will last though. It would be very nice if new versions of Docker would always provide backwards-compatibility for older Docker images, even in 20-30 years.
I wrote a little blog post about my experience with Hugo - https://madebynathan.com/posts/2021-12-05-how-docker-saved-m...
I struggled with this issue when I realized that it was too much work to update my blog to use the latest version of Hugo. I wasn't able to run the old hugo binary on my new version of MacOS (segfault). And I couldn't even compile the old code from source, because I couldn't get older versions of Go to work. Some of the old Go dependencies had even been renamed or deleted.
Eventually I realized that I could continue using my old version of Hugo forever (0.21) if I run it in a Linux Docker container. The output is still static HTML and CSS, and all the static files are cached and served with a CDN (CloudFlare), so I'm not particularly worried about security updates.
I'm not sure how long this will last though. It would be very nice if new versions of Docker would always provide backwards-compatibility for older Docker images, even in 20-30 years.