Skip to content

ci: unpin the devcontainer's Hugo feature - #6554

Merged
max-sixty merged 1 commit into
mainfrom
ci/devcontainer-hugo-unpin
Nov 14, 2026
Merged

max-sixty merged 1 commit into
mainfrom
ci/devcontainer-hugo-unpin

Conversation

@prql-bot

@prql-bot prql-bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Collaborator

Removes the 0.169.0 pin #6553 put on the devcontainer's Hugo feature, restoring "ghcr.io/devcontainers/features/hugo:1": {} exactly as it was before. This PR's test-devcontainer run passes, installing Hugo through the feature's unpinned latest path, which today resolves to 0.170.0.

The likely cause of the #6552 failure is the feature's version lookup, not Hugo 0.170.0. On latest, the feature's install.sh asks the unauthenticated api.github.com/repos/gohugoio/hugo/releases/latest endpoint for the version and greps tag_name out of the reply. If that request is rate-limited, VERSION comes back empty and the download URL becomes releases/download/v/hugo__Linux-64bit.tar.gz, which returns 404, matching the curl: (22) ... 404 in the failed job. The 0.170.0 asset the feature builds, hugo_0.170.0_Linux-64bit.tar.gz, downloads with a 200, and the lookup parses 0.170.0 correctly when the API answers. Upstream has tracked this rate-limit fragility since 2023 in devcontainers/features#458. I couldn't see the URL the failing runner actually requested, and only one main run (plus its rerun) ran test-devcontainer after 0.170.0 shipped, so the release timing may be coincidence.

If that's right, an unpinned build can still fail now and then when the runner's IP is out of unauthenticated API quota. A pinned version avoids that, at the cost of bumping it by hand.

Refs #6552

@max-sixty
max-sixty merged commit 13e82db into main Nov 14, 2026
36 checks passed
@max-sixty
max-sixty deleted the ci/devcontainer-hugo-unpin branch November 14, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants