some notes on upgrading Hugo https://jvns.ca/blog/2024/10/07/some-notes-on-upgrading-hugo/

(yesterday I claimed I definitely was not going to upgrade Hugo but apparently I did in fact want to spend like 6 hours fixing Markdown problems for some reason)

Some notes on upgrading Hugo

Some notes on upgrading Hugo

Julia Evans
@b0rk there's no limit to what you can accomplish when you should be doing something else.
@b0rk a chill goes down my spine at the phrase ‘upgrading hugo’ 😵‍💫
@brhfl i would not recommend it
@b0rk i did it exactly one time, never again 😹
@b0rk @brhfl Some people volunteer as subjects for scientific experiments with unknown side-effects. Others upgrade Hugo and blog about it.
@b0rk I often cite your original blog post about trying to get hugo 0.4 to build as an example of the costs that backwards-incompatible changes cost your users (even if you semantically version them correctly!), in contrast to something like SQLite

@b0rk Kudos! 👏💪

Honestly, not sure whether the moral of the story is "never upgrade" or "upgrade all the time". 🤔

@b0rk Awesome! Skimming the HTML diff of my entire website after regenerating it with Hugo is oddly addictive.

(There's an incomplete sentence "and I’m not totally sure", I think.)

@b0rk > I ended up hacking together a bash script to download all of the changelogs from github as text files, which I could then grep to try to figure out what happened.

This is something that really bugs me about GitHubs release feature. If you get behind it’s very difficult (and time consuming) to read through all the release notes. And it’s especially bad if the project has frequent .rc releases both because they take up space and sometimes the breaking changes are only listed in the rc’s!

@b0rk Also thank you for documenting your upgrade process! That was a fun script to see the diffs!
@b0rk Great yakshaving post! Just fyi, the examples in 4.1 end in a ] and should end in a ). I think?
@b0rk I almost didn’t open the diff script. But I’m glad I did since I now know about git diff --no-index.
@b0rk 4.1 has a typo, the closing bracket should be a closing paren, right?