-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.139.5 release is missing assets causing GitHub workflow to fail #13150
Comments
Yes, sadly the newest release has a human readable message of
in it, but my automated workflows can't read English instructions like that, so they construct a download URL with 0.139.5 in, get a 404, and terminate in a failed state. Anyone who uses https://github.com/peaceiris/actions-hugo with a version of "latest" will be broken by this, for example. |
Yes, I also have this issue |
You need to use 0.139.4. 0.139.5 is there only to make |
Yeah, I have this problem, too. Setting the version as '0.139.4' is OK. |
I appreciate the hard work you invest into hugo! If at all possible it would be very valuable to add assets to the 0.139.5 release (or add a subsequent release with assets) since this breaks all builds that are relying on "latest" hugo and makes people like myself spend half an hour trying to figure out what is going on 😢 Pinning the version to 0.139.4 and then later remembering to unpin it is a feasible workaround. |
Release 0.139.5 contains no assets and was only made for technical reasons. The deployment fails with error: Error: Action failed with error Unexpected HTTP response: 404 See gohugoio/hugo#13150
Does not build with latest due to missing assets in current build (0.139.5), as per gohugoio/hugo#13150 Temporary fix is to set to previous version. Should be reverted to latest when resolved.
My automated GitHub Actions workflow fails due to missing assets in the 0.139.5 release.
The 0.139.5 release only contains:
Previous releases had ~29 assets, such as this list from 0.139.4:
The text was updated successfully, but these errors were encountered: