[TT-16950] fix: sync security hardening from release-5.12 (#7956) #8070
+157
−75
probelabs / Visor: performance
succeeded
Apr 17, 2026 in 1m 0s
✅ Check Passed (Warnings Found)
performance check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Performance (1)
⚠️ .github/workflows/ci-tests.yml:20 - The introduction of thedep-guardjob as a dependency for other jobs (likelint) adds a sequential step to the CI pipeline. This will increase the overall wall-clock time for workflows to complete on pull requests. This change is present in multiple workflow files (e.g.,codeql-analysis.yml,lint.yml,plugin-compiler-build.yml).
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 20 in .github/workflows/ci-tests.yml
probelabs / Visor: performance
performance Issue
The introduction of the `dep-guard` job as a dependency for other jobs (like `lint`) adds a sequential step to the CI pipeline. This will increase the overall wall-clock time for workflows to complete on pull requests. This change is present in multiple workflow files (e.g., `codeql-analysis.yml`, `lint.yml`, `plugin-compiler-build.yml`).
Raw output
This is an intentional trade-off for enhanced security. The impact on CI execution time should be monitored. If the `dep-guard` job becomes a significant bottleneck, consider if it can be run in parallel with other setup or non-dependent jobs to minimize its impact on the critical path of the workflow.
Loading