You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running any module commands, Hugo (Go) will add the patch release number to the go.mod file. This will in turn lead to an error as the code can't handle go versions with a patch, e.g. go 1.21.1
What version of Hugo are you using (hugo version)?
$ hugo version
hugo v0.119.0-b84644c008e0dc2c4b67bd69cccf87a41a03937e+extended darwin/arm64 BuildDate=2023-09-24T15:20:17Z VendorInfo=brew
$ go version
go version go1.21.2 darwin/arm64
Does this issue reproduce with the latest release?
Yes.
The text was updated successfully, but these errors were encountered:
Okay! I don't know what happened yesterday. I can't recreate this issue anymore.
The error I got last night was identical to what people report in this issue: golang/go#61888
Looking through issue reported in the Go repo, there seems to be a lot of related issues with people upgrading to v1.21.x. It seems that this is mostly fixed by upgrading Go.
I'm closing this as it is not a Hugo issue. And the fact that I can't recreate it, also offers zero help.
When running any module commands, Hugo (Go) will add the
patch
release number to thego.mod
file. This will in turn lead to an error as the code can't handlego
versions with a patch, e.g. go 1.21.1What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes.
The text was updated successfully, but these errors were encountered: