Squid 1.7.9
Bug fix: Skip Calamari for PowerShell scripts (was crashing with
FileNotFoundException).
Tentacle's StartProcess routed PowerShell + variables.json through the
Calamari child process, but Calamari has no PowerShell pipeline:
WriteBootstrappedBashScriptStep does File.ReadAllText("script.sh") and
the CLI is hardcoded to --script=script.sh. Result on every Windows IIS
deploy: FileNotFoundException → Calamari child died → state file stuck
at Progress=Running → server's GetStatus orphan-detection returned
Complete + UnknownResult (-1). Operator saw "Unknown result (ticket or
process not found) (exit code -1)".
Fix: IsCalamariCompatible(syntax) returns true ONLY for Bash. PowerShell
scripts now route through StartViaLauncher, which picks the right
launcher (pwsh-Core if installed, Windows PowerShell 5.1 fallback per
1.7.8's PR #352). Safe because all server-side PowerShell builders
already inline variables into the rendered script body — Calamari's
bootstrap preamble was adding zero value on top of that.