Hugo: Rework the min_version for theme components

[akshaybabloo]

Sometimes we might use SCSS and adding support for an extended version of Hugo in min_version would help others as a requirement. Example:

min_version = "0.51-extended"

[felicianotech]

I still dislike having a separate extended version in the first place. My first choice would be to have a single build.

If that doesn't happen, then this makes sense.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[akshaybabloo]

Adding text so that the bot doesn't close this issue.

[bep]

I'm soon going to release a Hugo version with what we somehow have agreed to name Hugo Modules which I'm certain that you will really, really like. And with that, these interop issues gets even more important to warn about.

What suggest is that we replace what we have (the old will still work), with a hugo_version config that you can set in theme.toml, variants being:

hugo_version:
    min: "0.55.0"

hugo_version:
    min: "0.52.0"
    max: "0.55.0"

hugo_version:
    min: "0.52.0"
    max: "0.55.0"
    features: ["scss"]

Note that I'm happy to discuss making the extended version the "regular" one for Linux, MacOS, and Windows, but as we do support many others, there is no short term realism in getting rid of the extended build for FreeBSD and all the others. I spent a good day getting the current extended builds running, and those were the platforms I could easily test on ... Do the math.

I'm not totally sure what the current values for features would be, but I thought it would be better to say scss than extended.

Any thougts/objections to the above?

/cc @regisphilibert and gang

[regisphilibert]

I love that you can add a max version as well.

If we name the last key features, I'm afraid people might mistake it for some Hugo features required by the theme. As in Pipes, Related etc...

Can we limit the extended build to doing scss and if another build variation is needed, will it be about just one feature as well?

I am not sure how build variation (already I am doing a poor job at defining it) should be labeled, and if more are going to come, but feature is kind of misleading.

[bep]

@regisphilibert you're right. By making it a config struct we can be explicit about it:

hugo_version:
    min: "0.52.0"
    max: "0.55.0"
    extended: true

[bep]

I'll handle this as part of #5996