Thank you everyone for the comments thus far.
How far back? Does that depend on your oldest site? Or do you just keep maybe the last 5 versions or something?
How do you go about testing your theme? The Hugo demo site? A personal site? Multiple?
We all start off as beginners. Thank you for sharing.
Interesting, is this something you do via Homebrew itself (the pinning)?
Haven’t heard of that before. That sounds like it might be useful. I’ll see if I can work something like that out in my workflow.
In case anyone was curious where these questions are coming from, here it is.
I build all of my Hugo websites (at least 4 public as of now) with CircleCI. I use the Hugo Docker Image I created specifically to help test the sites. It test to make sure Hugo itself completes successfully, but also HTML quality and broken links.
I’m trying to determine how many versions back of Hugo should be supported in this image. This means 2 different things:
- The existence of the Docker tag for a Hugo version itself. Without this, you wouldn’t be able to use this Hugo version at all.
- When to “update” the image. Aside from Hugo, underlying tools such as the version of Ruby, HTML Proofer, and Nokogiri can change. Should I update an existing Hugo Docker image that is already made with newer versions of these tools? Or just when a new version of Hugo is released?
Also, I have a single public theme but I hope to create more in the future. I would like to come up with a CI process in order to test Hugo themes with several versions of Hugo. It would be great to have automated testing that says, "Hey, this Hugo theme has been tested with Hugo versions 0.28, 0.29, and 0.30.2 and should work fine.
Similar to how an open-source Python project might test with multiple versions of Python (both major and minor releases).
To that end, I’m trying to to figure out how often and how people update to newer versions of Hugo. Myself, I update my Docker image to support the newest version of Hugo usually within 12 hours. I then have my sites upgrade to that new version the next time I touch that site, whatever reason that may be.