All Versions
66
Latest Version
Avg Release Cycle
10 days
Latest Release
1237 days ago

Changelog History
Page 5

  • v0.63.0 Changes

    January 23, 2020

    Hugo 0.63 is, in general, considerably faster and more memory effective (see the site-building benchmarks below comparing it to v0.62). Not that we are particularly concerned about Hugo's build speed. We leave that to others. But we would hate if it got slower, so we have a comprehensive benchmark suite. And when we needed to simplify the template handling code to solve a concurrency issue, it also became more effective. And as a bonus, we also finally got the base template lookup order that you really, really wanted!

    name old time/op new time/op delta SiteNew/Bundle\_with\_image-16 13.2ms ± 2% 10.7ms ± 0% -19.13% (p=0.029 n=4+4) SiteNew/Bundle\_with\_JSON\_file-16 13.1ms ± 0% 10.8ms ± 0% -17.50% (p=0.029 n=4+4) SiteNew/Tags\_and\_categories-16 47.7ms ± 1% 43.7ms ± 2% -8.43% (p=0.029 n=4+4) SiteNew/Canonify\_URLs-16 52.3ms ± 6% 49.5ms ± 7% ~ (p=0.200 n=4+4) SiteNew/Deep\_content\_tree-16 77.7ms ± 0% 71.6ms ± 1% -7.84% (p=0.029 n=4+4) SiteNew/Many\_HTML\_templates-16 44.0ms ± 2% 37.5ms ± 1% -14.79% (p=0.029 n=4+4) SiteNew/Page\_collections-16 58.4ms ± 1% 52.5ms ± 1% -10.09% (p=0.029 n=4+4) name old alloc/op new alloc/op delta SiteNew/Bundle\_with\_image-16 3.81MB ± 0% 2.22MB ± 0% -41.57% (p=0.029 n=4+4) SiteNew/Bundle\_with\_JSON\_file-16 3.60MB ± 0% 2.01MB ± 0% -44.09% (p=0.029 n=4+4) SiteNew/Tags\_and\_categories-16 19.3MB ± 1% 14.2MB ± 0% -26.52% (p=0.029 n=4+4) SiteNew/Canonify\_URLs-16 70.7MB ± 0% 69.0MB ± 0% -2.30% (p=0.029 n=4+4) SiteNew/Deep\_content\_tree-16 37.0MB ± 0% 31.2MB ± 0% -15.78% (p=0.029 n=4+4) SiteNew/Many\_HTML\_templates-16 17.5MB ± 0% 10.6MB ± 0% -39.68% (p=0.029 n=4+4) SiteNew/Page\_collections-16 25.8MB ± 0% 21.2MB ± 0% -17.80% (p=0.029 n=4+4) name old allocs/op new allocs/op delta SiteNew/Bundle\_with\_image-16 52.3k ± 0% 26.1k ± 0% -50.08% (p=0.029 n=4+4) SiteNew/Bundle\_with\_JSON\_file-16 52.3k ± 0% 26.1k ± 0% -50.06% (p=0.029 n=4+4) SiteNew/Tags\_and\_categories-16 337k ± 1% 272k ± 0% -19.20% (p=0.029 n=4+4) SiteNew/Canonify\_URLs-16 422k ± 0% 395k ± 0% -6.33% (p=0.029 n=4+4) SiteNew/Deep\_content\_tree-16 400k ± 0% 314k ± 0% -21.41% (p=0.029 n=4+4) SiteNew/Many\_HTML\_templates-16 247k ± 0% 143k ± 0% -41.84% (p=0.029 n=4+4) SiteNew/Page\_collections-16 282k ± 0% 207k ± 0% -26.31% (p=0.029 n=4+4)

    This release represents 35 contributions by 9 contributors to the main Hugo code base. @bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @hcwong, @flother, and @RemcodM 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 @davidsneighbour and @kaushalmodi for all the great work on the documentation site.

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

    Hugo now has:

    Notes

    • 👀 .Type on-page now returns an empty string if not set in the front matter or if .Section returns empty. See #6760.
    • 👀 Baseof template (e.g. baseof.html) lookup order is completely revised/expanded. See base template lookup order. We now do template resolution at execution time following the same rules as the template it applies to (e.g. _default/single.html). This is an obvious improvement and your site should work as before.
    • 👍 Shortcode params now supports params with raw string literals (strings surrounded with ``) that supports newlines.
      Note: In a base template (e.g. baseof.html), the first template block must be a define.

    ✨ Enhancements

    Templates

    Output

    • ➕ Add base template lookup variant to docs.json cafb1d53 @bep

    Core

    Other

    🛠 Fixes

    Templates

    Core

    Other

  • v0.62.2 Changes

    January 05, 2020

    🚀 The main driving force behind these patch releases in the new year has been getting a good story with portable links between GitHub and Hugo, using the new render hooks introduced in Hugo 0.62.0. And all was mostly well until a Hugo user asked about anchor links. Which is, when you look into it, a slightly sad Markdown story. They have been talking about anchors in Markdown over at the CommonMark forum for the last six years, but it has come to nothing. The current situation is that some Markdown engines support the {#anchorName} attribute syntax (Hugo's Goldmark does, GitHub does not) and for those that support auto-generation of IDs, the implementation often varies. And this makes for poor portability.

    🔧 To improve this, Hugo has now reverse-engineered GitHub's implementation and made that the default strategy for generation or header IDs. We understand that this isn't everyone's cup of tea, so you can configure the behaviour to be one of github, github-ascii (some client-libraries have Unicode issues) or blackfriday (which will match how it behaved before Hugo 0.60).

  • v0.62.1 Changes

    January 01, 2020

    🚀 This release is mainly motivated by getting this demo site up and running. It demonstrates truly portable Markdown links and images, whether browsed on GitHub or deployed as a Hugo site.

  • v0.62.0 Changes

    December 23, 2019

    From all of us to all of you, a very Merry Christmas -- and Hugo 0.62.0! This version brings Markdown Render Hooks. This gives you full control over how links and images in Markdown are rendered without using any shortcodes. With this, you can get Markdown links that work on both GitHub and Hugo, resize images etc. It is a very long sought after feature, that has been hard to tackle until we got Goldmark, the new Markdown engine, by @yuin. When you read up on this new feature in the documentation, also note the new .RenderString method on Page.

    Adding these render hooks also had the nice side effect of making Hugo faster and more memory effective. We could have just added this feature on top of what we got, getting it to work. But you like Hugo's fast builds, you love instant browser-refreshes on change. So we had to take a step back and redesign how we detect "what changed?" for templates referenced from content files, either directly or indirectly. And by doing that we greatly simplified how we handle all the templates. Which accidentally makes this version the fastest to date. It's not an "every site will be much faster" statement. This depends. Sites with many languages and/or many templates will benefit more from this. We have benchmarks with site-building showing about 15% improvement in build speed and memory efficiency.

    This release represents 25 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 @gavinhoward, @niklasfasching, and @zaitseff 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 8 contributions by 5 contributors. A special thanks to @bep, @DirtyF, @pfhawkins, and @bubelov for their work on the documentation site.

    Also a big shoutout and thanks to the very active and helpful moderators on the Hugo Discourse, making it a first class forum for Hugo questions and discussions.

    Hugo now has:

    Notes

    • 👀 Ace and Amber support is now removed from Hugo. See #6609 for more information.
    • 👍 The markdownify template function does not, yet, support render hooks. We recommend you look at the new and more powerful .RenderString method on Page.
    • 🚀 If you have output format specific behaviour in a template used from a content file, you must create a output format specific template, e.g. myshortcode.amp.html. This also applies to the new rendering hooks introduced in this release. This has been the intended behaviour all the time, but a failing test (now fixed) shows that the implementation of this has not been as strict as specified, hence this note.
    • 🖨 The errorf does not return any value anymore. This means that the ERROR will just be printed to the console. We have also added a warnf template func.

    ✨ Enhancements

    Templates

    Core

    • 👌 Improve error and reload handling of hook templates in server mode 8a58ebb3 @bep #6635

    Other

    🛠 Fixes

    Templates

    Core

    Other

  • v0.61.0 Changes

    December 11, 2019

    🚀 This is the 40K GitHub Stars Edition. It's mostly a bug fix release, and an important note is the deprecation of Amber and Ace as template engines. See #6609 for more information.

    This release represents 10 contributions by 3 contributors to the main Hugo code base.

    📚 Many have also been busy writing and fixing the documentation in hugoDocs,
    which has received 5 contributions by 4 contributors. A special thanks to @YuriyOborozhnyi, @bep, @Flogex, and @atishay for their work on the documentation site.

    Hugo now has:

    Notes

    ✨ Enhancements

    Templates

    Other

    🛠 Fixes

    Core

    Other

  • v0.60.1 Changes

    November 29, 2019

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

  • v0.60.0 Changes

    November 27, 2019

    👀 Goldmark by @yuin is now the new default library used for Markdown in Hugo. It's CommonMark compliant and GitHub flavored, and both fast and flexible. Blackfriday, the old default, has served us well, but there have been formatting and portability issues that were hard to work around. The "CommonMark compliant" part is the main selling feature of Goldmark, but with that you also get attribute syntax on headers and code blocks (for code blocks you can turn on/off line numbers and highlight line ranges), strikethrough support and an improved and configurable implementation of TableOfContents. See Markup Configuration for an overview of extensions.

    📚 Please read the Notes Section and the updated documentation. We suggest you start with List of content formats in Hugo. Goldmark is better, but the feature set is not fully comparable and it may be more stricter in some areas (there are 17 rules for how a headline should look like); if you have any problems you cannot work around, see Configure Markup for a way to change the default Markdown handler.

    Also, if you have lots of inline HTML in your Markdown files, you may have to enable the unsafe mode:

    markup: goldmark: renderer: unsafe: true

    This release represents 62 contributions by 10 contributors to the main Hugo code base. @bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @anthonyfok, @max-arnold, and @trimbo 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 and @davidsneighbour for great work on the documentation site.

    📚 Many have also been busy writing and fixing the documentation in hugoDocs,
    which has received 8 contributions by 4 contributors. A special thanks to @bep, @jasdeepgill, @luucamay, and @jkreft-usgs for their work on the documentation site.

    Hugo now has:

    Notes

    • 👍 Permalink config now supports Go date format strings. #6489
    • 🚚 We have removed the option to use Pygments as a highlighter. #4491
    • 0️⃣ Config option for code highlighting of code fences in Markdown is now default on. This is what most people wants.
    • 📚 There are some differences in the feature set of Goldmark and Blackfriday. See the documentation for details.
    • The highlight shortcode/template func and the code fence attributes now share the same API regarding line numbers and highlight ranges.
    • 🔧 The Total in ... for the hugo command now includes the configuration and modules loading, which should make it more honest/accurate.
    • The image logic in the 3 SEO internal templates twitter_cards.html, opengraph.html, and schema.html is consolidated: images page param first, then bundled image matching *feature*, *cover* or *thumbnail*, then finally images site param.
    • 🗄 Deprecate mmark 33d73330 @bep #6486

    ✨ Enhancements

    Templates

    Output

    Core

    Other

    🛠 Fixes

    Output

    Core

    Other

  • v0.59.1 Changes

    October 31, 2019

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

  • v0.59.0 Changes

    October 21, 2019

    🚀 The timing of this release is motivated by getting the copies of the docs repositories in synch, now fully "Hugo Modularized". But it also comes with some very nice additions:

    It is now possible to set the target format and the background fill color when processing images, e.g.:

    {{ $image.Resize "600x jpg #b31280" }}

    👀 See Image Processing Options.

    Another useful addon is the $pages.Next and $pages.Prev methods on the core page collections in Hugo. These works the same way as the built-in static variants one Page, e.g. .Next and .NextInSection:

    {{with .Site.RegularPages.Next . }}{{.RelPermalink}}{{end}}

    The above is a functionally equivalent (but slightly slower) variant of:

    {{with .Next }}{{.RelPermalink}}{{end}}

    👀 See Pages Methods for more information.

    This release represents 45 contributions by 13 contributors to the main Hugo code base. @bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @anthonyfok, @BaibhaVatsa, and @XhmikosR 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 34 contributions by 20 contributors. A special thanks to @bep, @celtic-coder, @napcs, and @bmackinney for their work on the documentation site.

    Hugo now has:

    Notes

    • 👀 Shortcode params can now be typed (supported types are string, bool int and float64, see #6376.
    • 🚀 Pages.Next/.Prev as described above has existed for a long time, but they have been undocumented. They have been reimplemented for this release and now works like their namesakes on Page. This may be considered a breaking change, but it should be a welcome one, as the old behaviour wasn't very useful. See #4500

    ✨ Enhancements

    Templates

    Output

    Other

    🛠 Fixes

    Core

    Other

  • v0.58.3 Changes

    September 19, 2019

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