fix: correct step-security/harden-runner SHA in merge conflict bot workflow #1280
StepSecurity Actions Security / StepSecurity Harden-Runner
succeeded
Dec 31, 2025 in 28s
No anomalous activity on CI/CD runners
No new Harden-Runner detections for this pull request.
Details
Harden-Runner monitors all outbound traffic from each job at the DNS and network layers to ensure that CI/CD runners do not communicate with unauthorized destinations.
This reduces the risk of CI/CD secrets and source code being exfiltrated.
📋 Monitored GitHub Actions workflow runs
The following GitHub Actions workflow runs were monitored as part of this pull request.
| Workflow | Run ID | Unique Destinations | Actions Used | Detailed Insights |
|---|---|---|---|---|
| bot-merge-conflict.yml | 20625299880 | - | - | Harden-Runner not enabled |
| pr-check-test.yml | 20625300310 | 47 | 8 | View Insights |
| pr-check-broken-links.yml | 20625300303 | 2 | 3 | View Insights |
| pr-check-codecov.yml | 20625300297 | - | - | Harden-Runner not enabled |
| pr-check-examples.yml | 20625300300 | 41 | 8 | View Insights |
| pr-check-changelog.yml | 20625300298 | 1 | 2 | View Insights |
| bot-verified-commits.yml | 20625299894 | 1 | 1 | View Insights |
| pr-check-title.yml | 20625299905 | 2 | 2 | View Insights |
📚 Learn More
You can learn more about this GitHub check here
Loading