kube-score score exits 1 on any [CRITICAL] finding; the workflow's StatefulSets emit several (no resource limits, no liveness/readiness probes on init containers, etc). The prior ludovico85/kube-score-action@v1 wrapper did not propagate that exit code, mirroring how the slither scan ran. Trailing || true restores that no-block behaviour so reviewers see the findings without the job failing on them.
Switch to set -e and drop || true if findings should gate.
Co-Authored-By: Nakamoto, S <[email protected]>
Devin AIandNakamoto, S <[email protected]>
c0683a26a9