Was there another delete of a release and recreation?
My build has been failing for 2 days, which looks about the time the build started faining and I found reports of support: Hugo version v0.139.5 is not supported · Issue #662 · peaceiris/actions-hugo.
This is the second time this type of issue has developed recently.
Is this a temorary glitchy thing or something that will continue to happen?
p.s. Supper apriciate the work done on Hugo 
Current problems with latest seems to be caused by gohugoio/hugo#13147. v0.139.5 does not include any assets, which the action is trying to fetch.
##[debug]Failed to download from "https://github.com/gohugoio/hugo/releases/download/v0.139.5/hugo_extended_0.139.5_Linux-
Would it be posible for this to be automated?
For example I create releases manually to push new versions, but then the build automation automatically updates the assets so there is never a build without assets.
I have faced the same issue on a couple of sites where I set the action to use “latest” version of Hypha.
Locking the version to e.g. “0.139.4” makes it work again.
I normally do lock the version since the sites may run for years with little input from me and I do not want them to break.
But for some sites that I actively work on I do deploy with “latest” so it would be nice if this issue could be avoided.
This was a stupid mistake by me and should (almost) never happen.
On the brighter side, there will be a v0.140.0 release in a day or two.
No worries bep. I learned something new.
I am using hugo as a DevContainer feature and it defaults to latest.
If you are in that boat, set the version like this without a “v”.
“features”: {
"ghcr.io/devcontainers/features/hugo:1": {
“extended”: true,
“version”: “0.139.4”
},
"ghcr.io/devcontainers/features/go:1": {
“version”: “latest”
}
}
Cool! I added the abolity to pass the version as a varaible… so I dont need to update the build next time to fix