Eh. It’s written in go. I just built the binary, stuffed it in my repo and continued to use the same version for years. Then when I wanted to update I rewrote my whole theme from scratch, recompiled and now I’m set for years again.
I have a docker image with a given version of Hugo and I've been using it for years now.
That's the beauty of building HTML: you don't HAVE to stay up to date to get security fixes.
~/.local/bin/hugo0.145.0
~/.local/bin/hugo0.148.0
~/.local/bin/hugo0.149.0
~/.local/bin/hugo0.150.0
[...]
and a convenience symlink ~/.local/bin/hugo, pointing to my "production" version. I can easliy call whichever version I like with hugo<tab><tab>. What am I missing? - sharing it easily between computers/users (docker pull registry/image:tag)
- having the appropriate binary version embedded in your code through a docker-compose in your repo
- having custom aliases dedicated to hugo included (build/serve/run...)
- using the exact same image in your CI/CD
- not "polluting" your local computer with some more stuffI think that's what OP complains about here