deployment does not fail when hugo version cannot be downloaded #11

Open
opened 2025-12-08 11:18:57 +00:00 by devydave · 3 comments
Owner

In my case I deployed the app successfully, but the hugo version could not be downloaded. An the version fallback is 0.130. Hugo introduced a new (breaking, in some cases) template structure in 0.146 https://gohugo.io/templates/new-templatesystem-overview/. The result was every build failed.

In my case I deployed the app successfully, but the hugo version could not be downloaded. An the version fallback is 0.130. Hugo introduced a new (breaking, in some cases) template structure in 0.146 https://gohugo.io/templates/new-templatesystem-overview/. The result was every build failed.
Owner

@devydave do we need to bump the default version?

# set the used Hugo version optionally, otherwise the version defined in site-badger is used
#HUGO_VERSION=0.143.1

@devydave do we need to bump the default version? https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/commit/80ebe6e966234b5194c71f0980670be27239793d/.env.sample#L10-L11
Author
Owner

@decentral1se The issue came up again after updating to the newest release, we set the HUGO_VERSION, but the request failed and we get the old 0.130.0 version. We are currently debugging it

@decentral1se The issue came up again after updating to the newest release, we set the HUGO_VERSION, but the request failed and we get the old 0.130.0 version. We are currently debugging it
Author
Owner

Ok the error was copying the version tag from Github. The release is v0.130.0 but the recipe takes 0.130.0 as version without the v.
But i think it is still helpful to fail the deployment if there are errors in the HUGO_VERSION

Ok the error was copying the version tag from Github. The release is v0.130.0 but the recipe takes 0.130.0 as version without the v. But i think it is still helpful to fail the deployment if there are errors in the HUGO_VERSION
Sign in to join this conversation.