ci: fix three workflow infrastructure bugs (upload-artifact SHA, setup-beam ubuntu24, workflow-linter self-match)#3
Merged
Conversation
The pinned SHA 65c79d7f54e76e4e3c7a8f34db0f4ac8b515c478 doesn't exist in actions/upload-artifact, so the runner errors with "Unable to resolve action ... unable to find version" and Hypatia scans never start. Pinned to v4.6.2 (ea165f8d65b6e75b540449e92b4886f43607fa02), which is the latest v4 series matching the original `# v4` comment.
Two more CI infra fixes uncovered while sorting PR #2: * hypatia-scan.yml: setup-beam@v1.18.2 doesn't recognise ImageOS ubuntu24, so every Hypatia run aborts with "Tried to map a target OS from env. variable 'ImageOS' (got ubuntu24), but failed." Bumped to v1.24.0 (8d44588995...), which lists ubuntu-24.04 support in its README. * workflow-linter.yml: the SHA-pinned-actions check ran `grep -rn "uses:" .github/workflows/`, which matches the linter's own explanatory comment `# Find any uses: lines that don't have @sha format`. The comment is then flagged as unpinned and the check fails on itself. Anchor the regex on leading-whitespace + the directive form `^[[:space:]]+uses:[[:space:]]` so comments no longer match.
hyperpolymath
changed the title
…rectory
\${{ env.HOME }} resolves the workflow's `env:` block, not the runner's
$HOME, so the previous `working-directory: \${{ env.HOME }}/hypatia`
expanded to /hypatia and the build step failed with
"working directory '/hypatia'. No such file or directory".
Use a shell `cd "$HOME/hypatia"` instead, matching how the Clone and
Run steps already address the path.
hyperpolymath
added a commit
that referenced
this pull request
May 19, 2026
…64) #3 isolated commit. ONLY placeholder SPDX lines staged; repo's other uncommitted WIP deliberately left untouched/unstaged. PLMP/PMLP + doubled = scaffold artifacts (LICENCE-POLICY.adoc A5), NOT relicensing. Diff-shape asserted (SPDX-only). Refs standards LICENCE-POLICY.adoc A5. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Three independent CI infra fixes, each blocking PR #2 (and any other PR that triggers these workflows).
1.
hypatia-scan.yml— bad upload-artifact SHAactions/upload-artifact@65c79d7f54e76e4e3c7a8f34db0f4ac8b515c478doesn't resolve to a real ref; every Hypatia run errors withUnable to resolve action ... unable to find version. Repinned tov4.6.2(ea165f8d65b6e75b540449e92b4886f43607fa02), the current latest v4 series matching the original# v4intent.2.
hypatia-scan.yml— setup-beam doesn't know ubuntu24erlef/setup-beam@v1.18.2predates ubuntu-24.04 and bails withTried to map a target OS from env. variable 'ImageOS' (got ubuntu24), but failed. Bumped tov1.24.0(8d44588995e53ce789721e96227122a67826542d); v1.24's README listsubuntu-24.04as supported.3.
workflow-linter.yml— SHA-pinned-actions check matches its own commentThe check ran
grep -rn "uses:" .github/workflows/against everything, then expected a 40-char hex pin. Its own explanatory comment# Find any uses: lines that don't have @SHA formatsurvives the filter — there's no SHA — and the check fails on itself. Anchored the regex on leading-whitespace + directive form (^[[:space:]]+uses:[[:space:]]); comments and freeform text no longer match.Test plan
vscode-extension/src/extension.tsflag is a separate decision — out of scope for this PR)🤖 Generated with Claude Code