[TT-16977] fix: prevent dep-guard from skipping downstream jobs on push #972
+22
−3
probelabs / Visor: quality
failed
Apr 17, 2026 in 40s
🚨 Check Failed
quality check failed because fail_if condition was met.
Details
📊 Summary
- Total Issues: 2
- Error Issues: 2
🔍 Failure Condition Results
Failed Conditions
- global_fail_if: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
- Severity: ❌ error
Issues by Category
Logic (2)
- ❌ .github/workflows/release.yml:398 - The
aggregator-ci-statusjob'sneedsare updated to includedep-guard, but the correspondingrunscript that checks job statuses has not been updated. The script'srequired_jobsvariable (not visible in the diff) still only listsgoreleaserandapi-tests. Consequently, a failure in thedep-guardjob will not be detected by this aggregate status check, potentially leading to a misleading "success" status for pull requests wheredep-guardfails. - ❌ system:0 - Global failure condition met: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check failure on line 398 in .github/workflows/release.yml
probelabs / Visor: quality
logic Issue
The `aggregator-ci-status` job's `needs` are updated to include `dep-guard`, but the corresponding `run` script that checks job statuses has not been updated. The script's `required_jobs` variable (not visible in the diff) still only lists `goreleaser` and `api-tests`. Consequently, a failure in the `dep-guard` job will not be detected by this aggregate status check, potentially leading to a misleading "success" status for pull requests where `dep-guard` fails.
Raw output
Modify the `run` script within the `aggregator-ci-status` job to include `dep-guard` in the `required_jobs` variable to ensure its status is correctly aggregated.
Loading