Module "XXX" is not compatible with this Hugo version: Min 0.110.0 extended

Hi,
I’m using Hugo v0.128.2 with Docsy theme v0.10.0.
When I run hugo server, the output shows warnings:

WARN  Module "project" is not compatible with this Hugo version: Min 0.110.0 extended; run "hugo mod graph" for more information.
WARN  Module "docsy" is not compatible with this Hugo version: Min 0.110.0 extended; run "hugo mod graph" for more information.

So I run hugo mod graph, and the output is as below:

WARN  Module "project" is not compatible with this Hugo version: Min 0.110.0 extended; run "hugo mod graph" for more information.
WARN  Module "docsy" is not compatible with this Hugo version: Min 0.110.0 extended; run "hugo mod graph" for more information.
project hugomods/bootstrap
hugomods/bootstrap hugomods/icons/vendors/bootstrap
hugomods/icons/vendors/bootstrap hugomods/icons
hugomods/icons/vendors/bootstrap twbs/icons
project docsy
docsy twbs/bootstrap
docsy FortAwesome/Font-Awesome

What should I do to make those warnings disappear?

Your hugo mod graph looks strange… (see examples in details)

I’m unable to reproduce it with the bare Hugo setup from docsy guide

  • check your Go version
  • check your hugo is really extended
  • update modules hugo mod get -u
  • what about hugomods maybe it affects

additional your hugo and go.* config files may help.

With this Hugo Env
hugo v0.128.2-de36c1a95d28595d8243fd8b891665b069ed0850+extended windows/amd64 BuildDate=2024-07-04T08:13:25Z VendorInfo=gohugoio
GOOS="windows"
GOARCH="amd64"
GOVERSION="go1.22.2"
github.com/sass/libsass="3.6.5"
github.com/webmproject/libwebp="v1.3.2"
following the bare docsy setup guide
hugo new site bla --format yaml
cd bla
npm install --save-dev autoprefixer
npm install --save-dev postcss-cli
npm install -D postcss
hugo mod init bla
Add docsy module to hugo.yaml
baseURL: https://example.org/
languageCode: en-us
title: My New Hugo Site

module:
  hugoVersion:
    extended: true
    min: 0.110.0
  imports:
    - path: github.com/google/docsy
      disable: false
output `hugo`
go: no module dependencies to download
go: added github.com/google/docsy v0.10.0
hugo: collected modules in 706 ms
Start building sites …
hugo v0.128.2-de36c1a95d28595d8243fd8b891665b069ed0850+extended windows/amd64 BuildDate=2024-07-04T08:13:25Z VendorInfo=gohugoio


                   | EN
-------------------+-----
  Pages            |  8
  Paginator pages  |  0
  Non-page files   |  0
  Static files     | 30
  Processed images |  0
  Aliases          |  0
  Cleaned          |  0

Total in 4201 ms
output `hugo mod graph`
bla github.com/google/docsy@v0.10.0
github.com/google/docsy@v0.10.0 github.com/twbs/bootstrap@v5.3.3+incompatible
github.com/google/docsy@v0.10.0 github.com/FortAwesome/Font-Awesome@v0.0.0-20240402185447-c0f460dca7f7
when I add `- path: github.com/hugomods/bootstrap` the output changes to:
bla github.com/google/docsy@v0.10.0
github.com/google/docsy@v0.10.0 github.com/twbs/bootstrap@v5.3.3+incompatible
github.com/google/docsy@v0.10.0 github.com/FortAwesome/Font-Awesome@v0.0.0-20240402185447-c0f460dca7f7
bla github.com/hugomods/bootstrap@v0.22.3
github.com/hugomods/bootstrap@v0.22.3 github.com/hugomods/icons/vendors/bootstrap@v0.5.7
github.com/hugomods/icons/vendors/bootstrap@v0.5.7 github.com/hugomods/icons@v0.6.4
github.com/hugomods/icons/vendors/bootstrap@v0.5.7 github.com/twbs/icons@v1.11.3
github.com/hugomods/bootstrap@v0.22.3 github.com/hugomods/images@v0.11.0
github.com/hugomods/bootstrap@v0.22.3 github.com/hugomods/base@v0.7.2
1 Like

I think you’re right! After the Hugo version on my machine is upgraded from 0.115.x to v0.128.x by the server administrator, the warnings start to appear.

I’ve tested on another machine with the same website, and it doesn’t have those warnings.
I’ll just ignore those warnings because I don’t have administrator permission to install/upgrade Go and Hugo.

Thank you!

I would not just sit on it. It may brake later

On your machine and the other

  • output of hugo env
  • content of go.mod and go.sum?

Did you try with my bare setup an your machine? If that works it seems somethin in your repo you could fix.
If not your admin could have a look

Maybe make a backup and try hugo mod tidy and hugo mod clean