mirror of https://github.com/wolfSSL/wolfssh.git
f8f580b878
The gate skipped SBOM generation and exited 0 whenever wolfssl's scripts/gen-sbom was absent, so the job could report success having never exercised `make sbom`. That was deliberate while the script was unmerged, but it landed on master in wolfSSL/wolfssl#10343. On master, a missing gen-sbom or one too old for --dep-wolfssl is a regression, so fail instead of skipping: a green run now always means the target was exercised and the wolfssl-dependency assertions ran. Only a deliberately pinned older wolfssl_ref still degrades to a skip. The ref is passed through env rather than interpolated into the shell script, to keep the workflow expression out of the command line. |
||
|---|---|---|
| .. | ||
| code-coverage.yml | ||
| codespell.yml | ||
| coverity-scan-fixes.yml | ||
| cppcheck.yml | ||
| interop-mlkem.yml | ||
| multi-compiler.yml | ||
| network-contention-test.yml | ||
| os-check.yml | ||
| paramiko-sftp-test.yml | ||
| sanitizer.yml | ||
| sbom.yml | ||
| scp-test.yml | ||
| sftp-test.yml | ||
| singlethread-check.yml | ||
| sshd-test.yml | ||
| test-fatfs.yml | ||
| tpm-ssh.yml | ||
| windows-check.yml | ||
| windows-sftp.yml | ||
| x509-interop.yml | ||
| zephyr.yml | ||