e3c874bc756eff597394e3a54938a64977de111c
The Gitea Act runner's Docker container does not reliably support $GITHUB_PATH or sourcing ~/.cargo/env across steps. Both mechanisms failed because the runner spawns a fresh shell for each step. Adopted the same pattern that already works for the Windows job: explicitly set PATH at the top of every step that calls cargo or npx tauri. This is the most portable approach across all runner environments (Act Docker containers, bare metal macOS, Windows). Build history shows Linux succeeded through run#46 (JS-based actions) and failed from run#49 onward (shell-based installs). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Description
Releases
128
Triple-C v0.1.92 (Linux)
Latest
Languages
TypeScript
50%
Rust
39.3%
Shell
8.3%
Dockerfile
1.8%
CSS
0.3%
Other
0.2%