| Filename | Latest commit message | Latest commit date |
|---|---|---|
f32e7b59f2
Some checks failed
Agent Joule Release (Linux) / linux (push) Successful in 25m46s
Agent Joule Release (Windows arm64) / windows_arm64 (push) Successful in 40m16s
Agent Joule Release (Linux arm64) / linux-arm64 (push) Successful in 52m25s
Agent Joule Release (macOS) / mac (aarch64, aarch64-apple-darwin) (push) Successful in 52m50s
Agent Joule Release (macOS) / mac (x86_64, x86_64-apple-darwin) (push) Successful in 56m58s
Agent Joule Release (Windows) / windows (push) Has been cancelled
All five release workflows used a bare `actions/checkout@v4`. On a tag push that is fine -- github.ref is the tag. On workflow_dispatch it is not: the action checks out the dispatch BRANCH, while the `tag` input only decides which release the assets get uploaded into. So re-running one leg to patch a single platform quietly publishes main-built binaries into an older tag's release, and nothing in the run output says so. That already happened. v0.3.9 was published 2026-08-24 and every asset was uploaded that day except the x86_64 Windows zip and installer, which were re-uploaded on 2026-08-25 from a later main. The scoop manifest still carries the original hash, so `scoop install agent-joule` on x86_64 fails a hash check against the artifact now being served. (arm64 matches; both macOS DMGs match the Homebrew cask.) Pinning checkout to `inputs.tag || github.ref` makes the tag authoritative in both trigger paths, so a release can only ever contain what its tag contains. This removes the reliance on the dispatcher hand-picking the right ref, which is what failed here. The stale scoop hash and the mismatched v0.3.9 Windows assets are NOT fixed by this commit -- they need a rebuild from the tag. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| agent-joule-release-linux-arm64.yml | ||
| agent-joule-release-linux.yml | ||
| agent-joule-release-mac.yml | ||
| agent-joule-release-windows-arm64.yml | ||
| agent-joule-release-windows.yml | ||