I have been successfully using a GitHub-hosted runner to test compatibility of my theme with macOS. However, with GitHub actions now updating the latest
version of the runner from macOS 12 to macOS 14, I found out my test script is no longer working properly. I’m not sure if this is an environment issue, an issue with the used Hugo binary wrapper, or an issue with Hugo itself. Perhaps someone on this forum has run into a similar issue?
I have set up a test repo on GitHub. The runner image uses npm to install the extended hugo binary (as used by the Bootstrap docs). Once the environment has been set up, a test script invokes hugo env
to display the environment. Next, the same script invokes hugo mod vendor
to test Hugo module compatibility.
On macOS 12, the output is the following:
> hugo env && hugo mod vendor
hugo v0.125.4-cc3574ef4f41fccbe88d9443ed066eb10867ada2+extended darwin/amd64 BuildDate=2024-04-25T13:27:26Z VendorInfo=gohugoio
GOOS="darwin"
GOARCH="amd64"
GOVERSION="go1.22.2"
github.com/sass/libsass="3.6.5"
github.com/webmproject/libwebp="v1.3.2"
hugo: downloading modules …
hugo: collected modules in 4241 ms
However, the same script fails when changing the runner to macOS 14:
> hugo env && hugo mod vendor
hugo v0.125.4-cc3574ef4f41fccbe88d9443ed066eb10867ada2+extended darwin/arm64 BuildDate=2024-04-25T13:27:26Z VendorInfo=gohugoio
GOOS="darwin"
GOARCH="arm64"
GOVERSION="go1.22.2"
github.com/sass/libsass="3.6.5"
github.com/webmproject/libwebp="v1.3.2"
Error: failed to load modules: failed to download modules: binary with name "go" not found
Error: Process completed with exit code 1.
The test results for macOS 12 and macOS 14 can be found here: