Release Hugo 0.86.0

config.toml

@@ -17,6 +17,12 @@ pluralizeListTitles = false
 # We do redirects via Netlify's _redirects file, generated by Hugo (see "outputs" below).
 disableAliases = true
 
+[minify]
+  [minify.tdewolff]
+    [minify.tdewolff.css]
+    [minify.tdewolff.html]
+      keepWhitespace = true
+
 [module]
   [module.hugoVersion]
     min = "0.56.0"

content/en/news/0.86.0-relnotes/index.md

@@ -1,8 +1,8 @@
 
 ---
 date: 2021-07-21
-title: "0.86.0"
+title: "Hugo 0.86.0: Cascade in Config"
-description: "0.86.0"
+description: "Hugo 0.86.0 adds cascade keyword to site config, much improved \"active menu item\" logic for section pages, and more."
 categories: ["Releases"]
 ---
 
@@ -10,7 +10,7 @@ categories: ["Releases"]
 
 You can now have a top level [cascade](https://gohugo.io/content-management/front-matter#front-matter-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](https://gohugo.io/content-management/menus/) works good, but hasn't been particulary easy to set the active menu state for section pages without a menu defintion. We have had the option [Section Menu for Lazy Bloggers](https://gohugo.io/templates/menu-templates/#section-menu-for-lazy-bloggers). That helped for the common case, but we have now made it behave more sensible out of the box: `$section.HasMenuCurrent` will now always return true for any descendant of that section. To support this for menu defintions in the site config, we have added a new `pageRef` option on [MenuEntry](https://gohugo.io/variables/menus/#menu-entry-variables):
+Hugo's [Menu system](https://gohugo.io/content-management/menus/) works good, but hasn't been particulary easy to set the active menu state for section pages without a menu defintion. We have had the option [Section Menu for Lazy Bloggers](https://gohugo.io/templates/menu-templates/#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 defintions in the site config, we have added a new `pageRef` option on [MenuEntry](https://gohugo.io/variables/menus/#menu-entry-variables):
 
 ```toml
 [[menus.main]]

data/docs.json

@@ -1677,6 +1677,9 @@
       "caches": {
         "_merge": "none"
       },
+      "cascade": {
+        "_merge": "none"
+      },
       "frontmatter": {
         "_merge": "none"
       },
@@ -1745,7 +1748,7 @@
           "keepDocumentTags": true,
           "keepEndTags": true,
           "keepQuotes": false,
-          "keepWhitespace": false
+          "keepWhitespace": true
         },
         "css": {
           "keepCSS2": true,
@@ -1756,7 +1759,8 @@
           "keepVarNames": false
         },
         "json": {
-          "precision": 0
+          "precision": 0,
+          "keepNumbers": false
         },
         "svg": {
           "precision": 0

netlify.toml

@@ -3,7 +3,7 @@ publish = "public"
 command = "hugo --gc --minify"
 
 [context.production.environment]
-HUGO_VERSION = "0.85.0"
+HUGO_VERSION = "0.86.0"
 HUGO_ENV = "production"
 HUGO_ENABLEGITINFO = "true"
 
@@ -11,20 +11,20 @@ HUGO_ENABLEGITINFO = "true"
 command = "hugo --gc --minify --enableGitInfo"
 
 [context.split1.environment]
-HUGO_VERSION = "0.85.0"
+HUGO_VERSION = "0.86.0"
 HUGO_ENV = "production"
 
 [context.deploy-preview]
 command = "hugo --gc --minify --buildFuture -b $DEPLOY_PRIME_URL"
 
 [context.deploy-preview.environment]
-HUGO_VERSION = "0.85.0"
+HUGO_VERSION = "0.86.0"
 
 [context.branch-deploy]
 command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"
 
 [context.branch-deploy.environment]
-HUGO_VERSION = "0.85.0"
+HUGO_VERSION = "0.86.0"
 
 [context.next.environment]
 HUGO_ENABLEGITINFO = "true"