Repository navigation
fix: pin the devcontainer's Hugo feature to 0.169.0 - #6553
Conversation
Hugo 0.170.0 no longer publishes the Linux-64bit release assets that the devcontainers Hugo feature downloads, so building the devcontainer fails with a 404. Refs #6552
prql-bot
left a comment
There was a problem hiding this comment.
The pin fixes CI, but the stated cause is wrong. v0.170.0 still publishes hugo_0.170.0_Linux-64bit.tar.gz, the exact name the feature's install.sh builds on x86_64. That asset was uploaded at 2026-11-13T14:47Z, before the failing run, and it downloads with a 200. The unpinned feature still 404s on the runner: a re-run of test-devcontainer on main failed again at 11:23Z, while this PR's run passed. So the 404 comes from a different URL, probably from the feature resolving latest with an unauthenticated api.github.com lookup. I couldn't confirm that from here.
As written, the comment sends a reader looking for an asset rename that never happened, and it makes the pin removable "once the upstream feature learns the new asset names", which will never happen. The suggestion below keeps only what's verified. I'll push it and correct the PR description to match.
|
can we now try to fix and unpin |
|
Opened #6554 to unpin. Its There isn't a code fix for us to make. The likely cause is the feature's own version lookup: it asks the unauthenticated GitHub API for the latest release, and when that request is rate-limited the version comes back empty and the download URL 404s. Upstream has tracked this since 2023 in devcontainers/features#458. So an unpinned build can still fail occasionally. Re-pinning avoids that, but the version then has to be bumped by hand. |
The
test-devcontainerjob has been failing onmainsince Hugo 0.170.0 came out on 2026-11-13. Theghcr.io/devcontainers/features/hugofeature (v1.1.3), left onlatest, fails withcurl: (22) The requested URL returned error: 404while installing Hugo (run 43587099796, and again on its re-run). This pins the feature to 0.169.0, the same way the DuckDB feature is held on 1.x a few lines below. This PR's owntest-devcontainerrun passes with the pin.The exact cause of the 404 is unconfirmed. 0.170.0 still publishes
hugo_0.170.0_Linux-64bit.tar.gz, the name the feature builds on x86_64, and that file downloads fine. The feature resolveslatestwith an unauthenticatedapi.github.comlookup, and a pinned version skips that lookup. That points at the lookup rather than the download, but I haven't seen the URL the runner requested. The pin can go once an unpinnedtest-devcontainerrun passes again. It doesn't affectbuild-web, which installs Hugo separately throughpeaceiris/actions-hugo.Refs #6552 — automated triage