OINK 1.3.2 — Hugo-only builds restored
OINK 1.3.2 removes the mandatory Dart Sass installation introduced in 1.3.1. Ordinary site builds and previews use Hugo Extended and its built-in LibSass. Main styles, ReDoc styles, dark syntax highlighting, and project SCSS hooks remain supported. All independent readability and FileTree fixes from 1.3.1 remain included.
Build requirements
Hugo Extended 0.166.0 is the minimum and default development and strict CI version. Go is needed to resolve Hugo Modules; no external Sass executable, Node.js, or npm is required for ordinary site builds.
Hugo Extended 0.168.0 can also build and preview the site. It reports an
upstream LibSass deprecation warning. This warning is accepted and remains
visible. If you use --panicOnWarning, it will fail the build; use 0.166.0 for
the strict publication gate. OINK does not suppress other warnings.
The default Hugo version stays pinned. Future upgrades must preserve the consumer dependency boundary. A Hugo release that removes built-in LibSass requires a separate compatibility decision.
Upgrade
Update the module pin:
Commit the updated go.mod and go.sum. Remove Sass installation steps that
were added solely for OINK 1.3.1, and set the default Hugo workflow version to
0.166.0. Sites using a vendored theme must refresh that copy as well.
Existing content, appearance settings, and project SCSS customizations need no migration. See the toolchain contract.
Validation
The theme’s focused compiler check builds real main and ReDoc styles with no
Sass executable on PATH. It checks project-variable and project-style hooks
and the dark Chroma palette. Hugo 0.166.0 uses strict warnings; the separate
0.168.0 case accepts only the known upstream LibSass warning.