can't install fontawesome module

[lgwapnitsky]

I haven't updated my hugo instance in a few months. I went to do so today with some new content and, while building, I received the following message:

go: github.com/gethinode/mod-fontawesome@v1.11.0: invalid version: go.mod has post-v1 module path "github.com/gethinode/mod-fontawesome/v2" at revision v1.11.0
Error: failed to get ["-u" "github.com/gethinode/mod-fontawesome"]: failed to execute 'go [get -u github.com/gethinode/mod-fontawesome]': failed to execute binary "go" with args [get -u github.com/gethinode/mod-fontawesome]: go: github.com/gethinode/mod-fontawesome@v1.11.0: invalid version: go.mod has post-v1 module path "github.com/gethinode/mod-fontawesome/v2" at revision v1.11.0

I tried to manually change the version, but am still not able to compile my site.

Please advise.

Thank you

[markdumay]

Can you try again? I’ve invalidated mod-fontawesome@v1.11.0, as it contained an incorrect v2 module version suffix.

[lgwapnitsky]

Just ran it and receiving the same error. Do I need to modify any files in my config?

…

Message ID: <gethinode/hinode/repo-discussions/1467/comments/13512642@ github.com>

[lgwapnitsky]

Jus downloaded update go.sum, go.mod and package*.json files. Re-ran and still the same issue

…

Message ID: <gethinode/hinode/repo-discussions/1467/comments/13512642@ > github.com> >

[lgwapnitsky]

_vendor/modules.txt still generates v 1.10.1

…

On Wed, Jun 18, 2025 at 3:46 PM Larry Wapnitsky ***@***.***> wrote: Jus downloaded update go.sum, go.mod and package*.json files. Re-ran and still the same issue > Message ID: <gethinode/hinode/repo-discussions/1467/comments/13512642@ >> github.com> >> >

[markdumay]

You're correct, the release status is simply ignored by the hugo mod command in this case. I've deleted the entire release including the faulty tag. You should be able to update & install the module as expected.

To share a bit more context; Hugo uses Go's module system under the hood. A caveat is that Go requires the go.mod file to include the major version. The challenge is to ensure the Git tag is in sync with the go.mod version. In the problem you encountered, the release tag signaled v1, while the go.mod file indicated v2.

The Hinode modules use semantic release to automatically create the release and version number. Most of the modules also use Husky to validate the commit messages. However, in this particular case I forgot to add the commit message BREAKING CHANGE. So the go.mod file did include a v2 suffix as required, however, semantic release created a minor version upgrade instead (v1.11.0). Unfortunately, this particular commit message cannot be tested by Husky.

[lgwapnitsky]

great. sort of working now, but it appears there have been some big changes of locations since I last updated hugo. Working on migrating it now. Thanks

…

On Thu, Jun 19, 2025 at 1:35 AM Mark Dumay ***@***.***> wrote: You're correct, the release status is simply ignored by the hugo mod command in this case. I've deleted the entire release including the faulty tag. You should be able to update & install the module as expected. To share a bit more context; Hugo uses Go's module system under the hood. A caveat is that Go requires the go.mod file to include the major version. The challenge is to ensure the Git tag is in sync with the go.mod version. In the problem you encountered, the release tag signaled v1, while the go.mod file indicated v2. The Hinode modules use semantic release <https://semantic-release.gitbook.io/semantic-release> to automatically create the release and version number. Most of the modules also use Husky <https://github.com/typicode/husky> to validate the commit messages. However, in this particular case I forgot to add the commit message BREAKING CHANGE. So the go.mod file did include a v2 suffix as required, however, semantic release created a minor version upgrade instead (v1.11.0). Unfortunately, this particular commit message cannot be tested by Husky. — Reply to this email directly, view it on GitHub <#1467 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6CFDJ576D37DX6L3IIID3EJDYPAVCNFSM6AAAAAB7TU3XIOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJRGYYTGMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[markdumay]

Yes, Hugo has had a few significant changes. I'm working to make Hinode fully compatible with the latest version, see this issue for more details. A beta release is available if you're interested. I still need to iron out a few bugs and update the documentation though.