ci: merge trivy scan into build.yml as separate job

[gmegidish]

No description provided.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f01ff807-264c-4e0c-b0b3-7c46cbf40aa8

📥 Commits

Reviewing files that changed from the base of the PR and between 4ebdd76 and a73607c.

📒 Files selected for processing (2)

• .github/workflows/build.yml
• .github/workflows/trivy.yml

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

---

Walkthrough

The pull request consolidates Trivy security scanning configuration by moving the job from a dedicated workflow file into the main build workflow. The standalone .github/workflows/trivy.yml file, which performed filesystem security scans with severity filtering for HIGH and CRITICAL issues, is removed. A new trivy job is added to .github/workflows/build.yml that performs the same scan operation, running on macos-latest and using the same pinned Trivy CLI version (0.69.3). This centralizes the security scanning step within the primary build workflow configuration.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch merge-trivy-into-build

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}