Skip to content

fix(ci): use sha256sum on Linux/Windows, shasum on macOS#2

Merged
xuzhougeng merged 1 commit intomainfrom
fix/windows-release-shasum
Apr 22, 2026
Merged

fix(ci): use sha256sum on Linux/Windows, shasum on macOS#2
xuzhougeng merged 1 commit intomainfrom
fix/windows-release-shasum

Conversation

@xuzhougeng
Copy link
Copy Markdown
Collaborator

Summary

Hotfix after merge of #1. The Release workflow's Build windows-x86_64 job failed at the Package step with:

```
D:\a_temp....sh: line 22: shasum: command not found
Error: Process completed with exit code 127.
```

GitHub's Windows runner image ships Git Bash without the Perl-based `shasum` tool, but it does ship `sha256sum` (from coreutils). macOS is the opposite. Fix: branch on `$RUNNER_OS`.

Repro: https://github.com/AI4S-YB/RustQC/actions/runs/24770337963

Test plan

  • Windows Release build (windows-x86_64) now packages and uploads successfully
  • Linux / macOS Release builds still pass (no regression)
  • The `.sha256` output has identical format across platforms: `<64 hex chars> `

🤖 Generated with Claude Code

The Release workflow's Windows build failed at the Package step
because `shasum` is not available in Windows Git Bash on GitHub
runners. macOS, on the other hand, ships `shasum` (Perl) but not
`sha256sum`.

Pick the right tool per OS so all three platforms produce an
identical `<archive>.sha256` output line (`<hex>  <filename>`).

Repro: https://github.com/AI4S-YB/RustQC/actions/runs/24770337963
(run after merge of #1; Windows job failed with `shasum: command
not found`).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@xuzhougeng xuzhougeng merged commit 952d057 into main Apr 22, 2026
8 checks passed
@xuzhougeng xuzhougeng deleted the fix/windows-release-shasum branch May 4, 2026 05:09
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.

1 participant