Repository navigation
ci: unpin the devcontainer's Hugo feature - #6554
Merged
Merged
Conversation
This was referenced Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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'stest-devcontainerrun passes, installing Hugo through the feature's unpinnedlatestpath, 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'sinstall.shasks the unauthenticatedapi.github.com/repos/gohugoio/hugo/releases/latestendpoint for the version and grepstag_nameout of the reply. If that request is rate-limited,VERSIONcomes back empty and the download URL becomesreleases/download/v/hugo__Linux-64bit.tar.gz, which returns 404, matching thecurl: (22) ... 404in 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) rantest-devcontainerafter 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