ci(security): pin trivy-action to an existing tag (v0.30.0) so the gate can resolve on Gitea Actions
MobilityOps acceptance / backend (push) Failing after 33s
MobilityOps acceptance / frontend (push) Successful in 33s
MobilityOps acceptance / e2e (push) Skipped

The first real platform runs (2026-08-17, new instance runner) failed at
'Unable to resolve 0.30.0: reference not found' - the tag exists only as v0.30.0.
Where present, the trufflehog GitHub Action (which fails under the act runner) is
replaced by the pinned trufflehog binary in filesystem mode next to gitleaks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Jens
2026-08-18 14:13:18 +02:00
co-authored by Claude Fable 5
parent ca66083c8b
commit a830e8a2d0
+1 -1
View File
@@ -22,7 +22,7 @@ jobs:
docker compose -p mobilityops-ci -f compose.yaml -f compose.test.yaml run --build --rm api ruff check app tests scripts docker compose -p mobilityops-ci -f compose.yaml -f compose.test.yaml run --build --rm api ruff check app tests scripts
docker compose -p mobilityops-ci -f compose.yaml -f compose.test.yaml run --rm api mypy app docker compose -p mobilityops-ci -f compose.yaml -f compose.test.yaml run --rm api mypy app
- name: Backend dependency vulnerability scan (HIGH/CRITICAL) - name: Backend dependency vulnerability scan (HIGH/CRITICAL)
uses: aquasecurity/trivy-action@0.30.0 uses: aquasecurity/trivy-action@v0.30.0
with: with:
scan-type: fs scan-type: fs
scan-ref: backend scan-ref: backend