From 75300b0c7a4a94c7a0a776cb2711d5f662423dd8 Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN Date: Thu, 20 Aug 2026 15:11:46 -0400 Subject: [PATCH] Use the build's own hash file, not shasum, which Windows does not have MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit With the Windows tests, build, smoke and npm-pack checks all green, the last red on that platform was a step I wrote: `shasum -a 256`, a Unix tool. build.mjs already writes dist/seedpass-js.mjs.sha256 over exactly the file users execute, so the workflow reads that instead of computing it again with whatever happens to be installed. Fewer assumptions and one fewer thing that can differ per platform — which is the entire point of this workflow. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN --- .github/workflows/ts-platform.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ts-platform.yml b/.github/workflows/ts-platform.yml index 1a7f189b..c466a95b 100644 --- a/.github/workflows/ts-platform.yml +++ b/.github/workflows/ts-platform.yml @@ -84,8 +84,12 @@ jobs: npm install "$TARBALL" > /dev/null ./node_modules/.bin/seedpass-js --version - name: Record the bundle hash + # build.mjs already writes dist/seedpass-js.mjs.sha256 over exactly + # the file users execute, so use that rather than reaching for + # `shasum` -- which does not exist on Windows, and was the last thing + # failing there after the tests themselves went green. run: | - shasum -a 256 packages/cli/dist/seedpass-js.mjs | awk '{print $1}' \ + cut -d' ' -f1 packages/cli/dist/seedpass-js.mjs.sha256 \ > "$RUNNER_TEMP/bundle.sha256" echo "${{ matrix.os }}: $(cat "$RUNNER_TEMP/bundle.sha256")" - uses: actions/upload-artifact@v4