All Versions
13
Latest Version
Avg Release Cycle
11 days
Latest Release
30 days ago

Changelog History
Page 1

  • v0.57.2

    August 17, 2019

    Hugo 0.57.0 had some well-intended breaking changes. And while they made a lot of sense, one of them made a little too much noise.

    🚀 This release reverts the behavior for .Pages on the home page to how it behaved in 0.56, but adds a WARNING telling you what to do to prepare for Hugo 0.58.

    In short, .Page home will from 0.58 only return its immediate children (sections and regular pages).

    🚀 In this release it returns .Site.RegularPages. So to prepare for Hugo 0.58 you can either use .Site.RegularPages in your home template, or if you have a general list.html or RSS template, you can do something like this:

    {{- $pctx := . -}}
    {{- if .IsHome -}}{{ $pctx = .Site }}{{- end -}}
    {{- $pages := $pctx.RegularPages -}}
    
  • v0.57.1

    August 15, 2019

    🚀 This is a bug-fix release with a couple of important fixes.

  • v0.57.0

    August 14, 2019

    Hugo 0.57 brings Cascading Front Matter , Alphabetical Sorting , Resources Loading from Assets with Wildcards. And more.

    Cascading Front Matter : We have added a new and powerful cascade keyword to Hugo's front matter. This can be added to any index node in _index.md. Any values in cascade will be merged into itself and all the descendants.

    title: "My Blog"icon: "world.png"cascade: icon: "flag.png"outputs: ["HTML"]type: "blog"
    

    It's worth noting that the cascade element itself will also be merged. Also, to grasp the full value of this feature, remember that front matter in Hugo is both data and behaviour : You can tell Hugo how to process a subset of the pages (some example keywords are layout, type, outputs, weight) using the cascade keyword, e.g. "I want this subsection to be rendered in both the HTML and Calendar Output Formats".

    👀 This feature is created by@regisphilibert and @bep See #6041 for details.

    🍱 Resources Loading from Assets with Wildcards : We have added two new sought after template functions to the resources namespace: resources.Match and resources.GetMatch. These behaves like their namesake methods on Page (with super-asterisk wildcard support), but searches in all the resources in Assets. E.g. {{ $prettyImages := resources.Match "images/**pretty.jpg" }} will give a slice of all "pretty pictures". Another relevant example: {{ $js := resources.Match "libs/*.js" | resources.Concat "js/bundle.js" }}.

    🐎 Performance: In general, this version is slightly faster and more memory effective. In particular, we have fixed a performance issue with the replacer step that greatly improves the build speed of certain large and content-rich sites (thanks to @vazrupe for the fix).

    This release represents 46 contributions by 8 contributors to the main Hugo code base.@bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @muesli, @XhmikosR, and @vazrupe for their ongoing contributions.

    📚 And a big thanks to @digitalcraftsman and @onedrawingperday for their relentless work on keeping the themes site in pristine condition and to @kaushalmodi for his great work on the documentation site.

    📚 Many have also been busy writing and fixing the documentation in hugoDocs,
    which has received 13 contributions by 7 contributors. A special thanks to @regisphilibert, @bep, @kenberkeley, and @davidsneighbour for their work on the documentation site.

    Hugo now has:

    Notes

    • All string sorting in Hugo is now alphabetical/lexicographical.
    • home.Pages now only returns pages in the top level section. Before this release, it included all regular pages in the site. This made it easy to list all the pages on home page, but it also meant that you needed to take special care if you wanted to navigate the page tree from top to bottom. If you need all regular pages, use .Site.RegularPages. Also see #6153.
    • 👀 .Pages now include sections. We have added .RegularPages as a convenience method if you want the old behaviour. See #6154 for details.
    • 👀 Hugo now only "auto create" sections for the home page and the top level folders. The other sections need a _index.md file. See #6171 for details.

    ✨ Enhancements

    Templates

    Core

    Other

    🛠 Fixes

    Core

    Other

  • v0.56.3

    July 31, 2019

    This is a bug-fix release with a couple of important fixes. After getting feedback about the new Hugo Modules feature, this release also adds some minor improvements:

    🚀 It adds support for overlapping file mounts, even for the filesystems where we walk down the directory structure. One relevant example that is fixed by this release:

    [module] [[module.mounts]]source="content1"target="content"[[module.mounts]]source="content2"target="content/docs"
    

    The above is obviously both common and very useful. This was never an issue with the situations where load a specific file/directory (e.g. resources.Get "a/b/c/d/sunset.jpg").

    🔧 User feedback also told us that these file mounts were a little hard to debug, so we added a new command that prints the configured mounts as a JSON:

    hugo config mounts
    
  • v0.56.2

    July 30, 2019

    🚀 This is a bug-fix release with a couple of important fixes.

  • v0.56.1

    July 28, 2019

    🚀 This is a bug-fix release with a couple of important fixes.

  • v0.56.0

    July 25, 2019

    Hugo 0.56.0 is filled with improvements, but there are two main headliners: Hugo Modules and Hugo Deploy.

    🚀 Hugo Deploy is implemented by @vangent and brings built-in deployment support for GCS, S3, or Azure using the Hugo CLI. See the Hugo Deploy Documentation for more information.

    Hugo Modules is very much a community effort on the design and specification side, but @bep has driven the implementation. Some notes about what all of this is about:

    • 🔧 A new module configuration section where you can import almost anything. You can configure both your own file mounts and the file mounts of the modules you import. This is the new recommended way of configuring what you earlier put in configDir, staticDir etc. And it also allows you to mount folders in non-Hugo-projects, e.g. the SCSS folder in the Bootstrap GitHub project.
    • 🍱 A module consists of a set of mounts to the standard 7 component types in Hugo: static, content, layouts, data, assets, i18n, and archetypes. Yes, Theme Components can now include content, which should be very useful, especially in bigger multilingual projects.
    • Modules not in your local file cache will be downloaded automatically and even "hot replaced" while the server is running.
    • 👍 Hugo Modules supports and encourages semver versioned modules, and uses the minimal version selection algorithm to resolve versions.
    • A new set of CLI commands are provided to manage all of this: hugo mod init, hugo mod get, hugo mod graph, hugo mod tidy, and hugo mod vendor.

    Hugo Modules is powered by Go Modules.

    This is all very much brand new and there are only a few example projects around:

    📚 See the Hugo Modules Documentation for more information.

    This release represents 104 contributions by 19 contributors to the main Hugo code base.
    @bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @vangent, @niklasfasching, and @coliff for their ongoing contributions.
    📚 And a big thanks to @digitalcraftsman and @onedrawingperday for their relentless work on keeping the themes site in pristine condition and to @kaushalmodi for his great work on the documentation site.

    📚 Many have also been busy writing and fixing the documentation in hugoDocs,
    which has received 48 contributions by 37 contributors. A special thanks to @davidsneighbour, @bep, @BCNelson, and @coliff for their work on the documentation site.

    Hugo now has:

    Notes

    🔧 We have removed the "auto theme namespacing" of params from theme configuration. This was an undocumented and hidden feature that wasn't useful in practice.

    👍 We have revised and improved the symlinks support in Hugo: In earlier versions, symlinks were only fully supported for the content folders. With the introduction of the new very flexible file mounts, with content support even for what we have traditionally named "themes", we needed a more precise definition of symlink support in Hugo:

    • Symlinks are not supported outside of the main project ((the project you run hugo or hugo server from).
    • In the main project static mounts, only symlinks to files are supported.
    • In all other mounts in the main project, both file and directory symlinks are allowed.

    ✨ Enhancements

    Templates

    Output

    Core

    Other

    🛠 Fixes

    Templates

    Output

    Core

    Other

  • v0.55.6

    May 18, 2019

    🚀 This is a bug-fix release with one important fix. There have been reports about infrequent paginator crashes when running the Hugo server since 0.55.0. The reason have been narrowed down to that of parallel rebuilds. This isn't a new thing, but the changes in 0.55.0 made it extra important to serialize the page initialization. This release fixes that by protecting the Build method with a lock when running in server mode. 95ce2a40 @bep #5885#5968

  • v0.55.5

    May 02, 2019

    🚀 This is a bug-fix release with a couple of important fixes.

    Hugo now has:

    ✨ Enhancements

    Templates

    Other

    🛠 Fixes

    Templates

    Output

    • 🛠 Fix permalink in sitemap etc. when multiple permalinkable output formats 6b76841b @bep #5910

    Core

    Other

  • v0.55.4

    April 25, 2019

    🚀 This is a bug-fix release with a couple of important fixes.

    Hugo now has:

    ✨ Enhancements

    Core

    Other

    🛠 Fixes

    Core