It’s worth noting that the issue that enabled/triggered the implementation of the above was the simplifications needed to fix #5903, which makes sure that type information is preserved when processed via Hugo Pipes. E.g. you can now do:
And it works as expected.
This release is also built with the brand new Go 1.13 which means that it’s also the fastest Hugo version to date.
This release represents 39 contributions by 5 contributors to the main Hugo code base.@bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @niklasfasching, @vazrupe, and @jakejarvis for their ongoing contributions.
home.Pages now behaves like all the other sections, see #6240. If you want to list all the regular pages, use .Site.RegularPages.
We have added some new image filters to Hugo’s image processing. This also means that we have consolidated the resize operations to use the one gift library (from the same developer as the one we used before). The operations work as before, but one difference is that we no longer embed color profile information in PNG images, but this should also be a more portable solution. Software that supports color profiles will assume that images without an embedded profile are in the sRGB profile. Software that doesn’t support color profiles will use the monitor’s profile, which is most likely to be sRGB as well.
We have improved the file cache logic for processed images and only stores them once when the same image is bundled in multiple languages. This means that you may want to run hugo --gc to clean your image cache.