Skip to content

OINK 0.8.2 — Go 1.26 module compatibility for the Hugo Themes builder

OINK 0.8.2 lowers the Hugo Module’s Go directive from 1.27 to 1.26 so GOTOOLCHAIN=local builders, including the official Hugo Themes pipeline, can import the theme without changing its Hugo floor or rendered behavior.

OINK 0.8.2 is a module-metadata compatibility release. It changes no template, asset, component API, configuration key, content syntax, or rendered output. Sites already using 0.8.1 need no content migration.

At a glance

  • The theme module now declares Go 1.26 instead of Go 1.27.
  • The official Hugo Themes builder can import OINK under its pinned Go 1.26 toolchain with GOTOOLCHAIN=local.
  • Hugo Extended 0.160.1 remains the declared compatibility floor; OINK Starter continues to build with Hugo Extended 0.165.0.
  • OINK contains no Go source and uses no Go 1.27 language or module feature, so the lower directive changes module admission only.

Why this patch exists

The OINK 0.8.1 release was built and tested with Go 1.27. Its go.mod therefore declared go 1.27.0, even though the repository is a Hugo Module made of templates and assets rather than Go packages. The official Hugo Themes pipeline runs Go 1.26 with automatic toolchain switching disabled. It correctly rejected the higher directive before reading the theme metadata.

OINK 0.8.2 declares the oldest Go toolchain the current release workflow needs: Go 1.26. The module remains byte-for-byte identical at the rendered surface; only the compatibility gate that admits the module has changed.

Compatibility

Dependency OINK 0.8.2 requirement
Hugo Extended 0.160.1 or newer
Go for Hugo Module resolution 1.26 or newer
Node.js Not required

An offline archive or Git submodule installation does not require Go because it does not ask Hugo to resolve a module.

Upgrade

hugo mod get github.com/pgsty/[email protected]
hugo mod tidy

Commit go.mod and go.sum, then run the site’s warning-strict production build. The complete change list is in CHANGELOG.md.