Hugo (gohugo) releases

computing
#1

In v1.talkgroup I used to publish and comment on Hugo updates individually, but now I’m just going to drop them all in this one topic, and we can comment/breakout as desired. :slight_smile:

#2

Poll based watching

Hugo 0.85.0: Polled based alternative when watching for changes and some other nice improvements.

July 5, 2021

Go to Hugo Releases for the release downloads.

Featured Image for Poll based watching

Hugo 0.85.0 is on the smaller side of releases, but the main new thing it brings should be important to those who need it: Poll based watching the filesystem for changes.

Hugo uses Fsnotify to provide native file system notifications. This is still the default, but there may situations where this isn’t working. The file may not support it (e.g. NFS), or you get the “too many open files” error and cannot or do not want to increase the ulimit. Enable polling by passing the --poll flag with an interval:

hugo server --poll 700ms

You van even do “long polling” by passing a long interval:

hugo server --poll 24h

This release represents 23 contributions by 6 contributors to the main Hugo code base.@bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @raoulb, @jmooring, and @digitalcraftsman for their ongoing contributions.

Many have also been busy writing and fixing the documentation in hugoDocs, which has received 1 contributions by 1 contributors.

Hugo now has:

Enhancements

Other

Fixes

Other

#3

Hugo 0.86.0: Cascade in Config

Hugo 0.86.0 adds cascade keyword to site config, much improved “active menu item” logic for section pages, and more.

July 21, 2021

Go to Hugo Releases for the release downloads.

Featured Image for Hugo 0.86.0: Cascade in Config

This release is a set of smaller fixes and improvements. Some of the more notable:

You can now have a top level cascade (or one per language, if needed) section in your site configuration (e.g. config.toml). This way you can control default front matter values from outside of the content files.

Hugo’s Menu system works well, but hasn’t been particularly easy to set the active menu state for section pages without a menu definition. We have had the option Section Menu for Lazy Bloggers. That helped for the common case, but we have now made it behave more sensible out of the box: $page.HasMenuCurrent $sectionMenuEntry will now always return true for any descendant of that section. To support this for menu definitions in the site config, we have added a new pageRef option on MenuEntry:

[[menus.main]]
pageRef = "blog"
# When pageRef is set, setting `url` is optional; it will be used as a fallback if the page is not found.
url = "/blog"

Set pageRef to a value that site.GetPage understands, and the menu entry will be correctly connected to the page.

This release represents 14 contributions by 2 contributors to the main Hugo code base. Many have also been busy writing and fixing the documentation in hugoDocs, which has received 1 contributions by 1 contributors.

Hugo now has:

Enhancements

Other

Fixes

Other

Haha, I’m so behind on Hgo releases! I mean, I read them fresh, but then I forget to post…

Cascading configuration is hot, allowing more flexibility with importing datasets: they don’t need their own front matter, as site-specific context may be provided. Neat!