Hugo did a massive overhaul of template lookups and setup that’s not even fully documented yet. Given the current pace of Hugo version changes, I doubt this is coming that fast, but given the scope of the change, I thought folks should be aware.
It does look like a better system, but it’s going to take a fair bit of changes across all themes.
Thanks for the heads-up! There are a lot of changes there.
I think we need to start keeping track of the minimum Hugo version number for each plug-in, so that Micro.blog can make sure the Hugo version matches up, and detect compatibility problems between conflicting plug-ins. Otherwise it’s going to be even more of a headache than it already is with our older Hugo versions.
I’ve been feeling nervous about this as well.
I’m going to put a max version for my themes and plugins this weekend in the hopes to avoid an issue.
[module]
[module.hugoVersion]
min = "0.117"
max = "0.117"
Ah, I’m glad there is a convention for this. Were you going to put these in your config.json file? I can update Micro.blog to look for the min and max versions.
I hade set it in the theme.toml a while ago. I only used min.
I’ll move it to the config.json, but I don’t think I need it because I’m pulling directly from GitHub.
It’s weird that this popped up today in my forum feed.