From bbaefd7e3e50935aa5cb2d907220e50a117aaf65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Erik=20Pedersen?= Date: Tue, 3 Mar 2020 16:10:16 +0100 Subject: [PATCH] Update 0.66.0-relnotes.md --- temp/{0.66.0-relnotes.md => 0.66.0-relnotes-ready.md} | 10 ++++++++++ 1 file changed, 10 insertions(+) rename temp/{0.66.0-relnotes.md => 0.66.0-relnotes-ready.md} (91%) diff --git a/temp/0.66.0-relnotes.md b/temp/0.66.0-relnotes-ready.md similarity index 91% rename from temp/0.66.0-relnotes.md rename to temp/0.66.0-relnotes-ready.md index c3effdaa1..925ff3530 100644 --- a/temp/0.66.0-relnotes.md +++ b/temp/0.66.0-relnotes-ready.md @@ -1,3 +1,13 @@ +This relase adds [inline `@import`](http://localhost:1313/hugo-pipes/postcss/#options) support to `resources.PostCSS`, with imports relative to Hugo's virtual, composable file system. Another useful addition is the new `build` [configuration section](http://localhost:1313/getting-started/configuration/#configure-build). As an example in `config.toml`: + +```toml +[build] + useResourceCacheWhen = "always" +``` + +The above will tell Hugo to _always_ used the cached build resources inside `resources/_gen` for the build steps requiring a non-standard dependency (PostCSS and SCSS/SASS). Valid values are `never`, `always` and `fallback` (default). + + This release represents **27 contributions by 8 contributors** to the main Hugo code base.[@bep](https://github.com/bep) leads the Hugo development with a significant amount of contributions, but also a big shoutout to [@anthonyfok](https://github.com/anthonyfok), [@carlmjohnson](https://github.com/carlmjohnson), and [@sams96](https://github.com/sams96) for their ongoing contributions. And a big thanks to [@digitalcraftsman](https://github.com/digitalcraftsman) and [@onedrawingperday](https://github.com/onedrawingperday) for their relentless work on keeping the themes site in pristine condition and to [@davidsneighbour](https://github.com/davidsneighbour) and [@kaushalmodi](https://github.com/kaushalmodi) for all the great work on the documentation site.