mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-12 13:47:16 -04:00
Cursor Agentandrmcrackan
b1452dabc3
The four dotnet publish calls share one run: block, and on windows-latest that block is pwsh. PowerShell does not stop at a native command that fails, and the step is judged by $LASTEXITCODE after the whole block, so only the last publish was ever able to fail the build. That is not hypothetical. LibationWinForms stopped compiling and every run since stayed green: the WinForms publish errored, the three after it succeeded, the step exited 0, and the job uploaded a Libation-Classic zip containing Hangover and the CLI but no Libation.exe at all. upload-artifact's if-no-files-found did not help, since the zip itself was there. Check the exit code after each publish, and refuse to package output with no Libation.exe in it - both UIs build under that name. Linux and macOS are not affected; their steps are bash, which Actions runs with -e. Co-authored-by: rmcrackan <rmcrackan@gmail.com>
