Got behind upgrading Hugo and realized I need to use one of the new “withdeploy” builds when I try to upgrade past 0.137.0… cool…
I’ve usually used the Debian release option from within my GitHub workflow to build & deploy my sites… but there’s no Debian option when using a “withdeploy” release.
Is this intentional and thus, I’ll need to switch my workflows to use one of the Linux x64 TAR release options?
Debian packages are controlled by Debian and the Debian package maintainers.
Debian packages are also generally a number of versions behind, by design.
I always download specific versions of Hugo for deployment. You can do it like the docs mention here Host on GitHub Pages | Hugo or make use of Hugo setup · Actions · GitHub Marketplace · GitHub.
When I said Debian packages, I mean the file as part of the release… the GH release. In my workflows, I download and install the Hugo package into the runner and then execute it.
The issue I’m facing that triggered this post was that I’m having issues executing the Hugo CLI after I unpack the TAR file for the new extended withdeploy releases.
Before I try to resolve that, I thought to ask if the deb release files were intentionally or mistakenly left out of the withdeploy options.
I understand, my mistake.
Looks like the asset build are controlled by this file Blaming hugo/hugoreleaser.toml at master · gohugoio/hugo · GitHub
Instructions to build a deb archive with “extended-withdeploy” are missing.
Let’s ask @bep what the reason for that is.
It was intentional as in: I defined the withdeploy for what I thought would be the most common variants. As to deb … well, I guess that was an oversight:
But this will not happen until next Hugo release.
Thanks @bep … I can wait until 0.141.0 unless there’s a good reason to switch to one of the other builds.
Not really … It’s just a config change, so it may get released in a 0.141.1 soonish if someone buggish happens.
I see this was resolved in 0.140.1… nice little present this holiday season @bep ! 
