Fix deadlock between ReschedulableTask::destroy() and concurrent task - #24
No anomalous activity on CI/CD runners
No new Harden-Runner detections for this pull request.
Approve a check
If you need to approve a check, please open a ticket with the SOC here: https://coveord.atlassian.net/servicedesk/customer/portal/116/group/640/create/1324Please include a link to the check.
We can create an exclusion if the call is expected. In the ticket, please specify the expected scope of the call: job, workflow, repository, or the entire org.
Re-run a check
To re-run a check, go to Conversation and add the following comment:@stepsecurity-app checks re-run
The check should re-run automatically. If it does not, open a ticket with the SOC here:
https://coveord.atlassian.net/servicedesk/customer/portal/116/group/244/create/589
Please include a link to the check.
No check should take more than 15 minutes. You can re-run a check if it does.
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 |
|---|---|---|---|---|
| tests.yml | 30929747799 | - | - | Harden-Runner not enabled |
📚 Learn More
You can learn more about this GitHub check here