enableInlineShortcodes moved into the new security config is a potentially breaking change.
Also this sounds exciting;
Hugo will soon introduce a concept of Content Source Plugins (AKA Pages from Data ), but the above will still hold true.
No, it’s not, it works both ways.
Hugo 0.91.0 packages
- traditional release - updated
- extended release - updated
Docker/CI Image - Hugo Docker image for Continuous Integration - updated
Docker Image - klakegg/hugo - Other Hugo Docker image - updated
Debian (sid) - updated (Track link)
Ubuntu (hirsute) - updated (Track link )
Fedora Copr - Hugo RPM package for Fedora and CentOS - not yet updated
Chocolatey Package - Hugo Chocolatey package for Windows
Nice to see this in the Security Model example, since this gives me hope it’s coming soon —
allow: - ^dart-sass-embedded$
That’s already there – you need to install the “embedded binary” yourself, but it works great.
Oh, yeah, have read about that over the months since the subject first arose, but I haven’t quite grasped how it would work in deployment — e.g., how to get the host to install it, too. (Am presuming that’s required.) Right now, I use environment vars per host to install the desired Hugo version but that’s because the host already installs a Hugo version, just not the one I want. Seems that, for Embedded Dart Sass, it would be a different situation. (For example, see this discussion, albeit from months ago, from the Netlify Community Forum.)
All that said, I’ll look again. Thanks.
Edit: And, after looking again, I’ve decided I’ll just wait for an official solution.
Docker image - klakegg/hugo - Updated
Brew - Hugo Brew package for macOS and Linux - updated
A post was split to a new topic: PostCSS error with snap install