Post by @benjamineskola@hachyderm.io

Henry
@hl @social.lol
Public en

The breaking changes in #Hugo do drive me crazy if you're not using it on an almost daily basis. I wanted to update one page in my blog, and since I last used Hugo it's gone from version 0.159.0 to 0.163.0, this now means the following things don't work:

  • Raw .html pages, I have to add a new config option to allow what is now considered insecure files to be added (0.162)
  • I can't use .Paginate on my 404 template page either (can't see the changelog for that)
  • At least there's a deprecation warning for .Site.LanguageCode being deprecated.

I wish they'd finally adopt semantic versioning, so you can prepare yourself and know when you're going to have to do extra work to get things to work again.

#StaticSite

Replying to @hl@social.lol
ben
@benjamineskola @hachyderm.io
Public en

@hl I think it was when they randomly dropped support for symlinks that I gave up on Hugo.

Replying to @benjamineskola@hachyderm.io
Henry
@hl @social.lol
Public en edited

@benjamineskola I have this sinking feeling that at some point, without warning, they'll drop org-mode support, which is the main, but niche, reason I picked Hugo over other SSGs, and then I'll have to find some other solution anyhow.