Skip to content

Fix: Freight should manage its own discoveryTimestamp, not rely on cr… #6133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2003Aditya wants to merge 1 commit into
base: main
Choose a base branch
from

Fix: Freight should manage its own discoveryTimestamp, not rely on cr…

5d8d499
Select commit
Loading
Failed to load commit list.
Open

Fix: Freight should manage its own discoveryTimestamp, not rely on cr… #6133

Fix: Freight should manage its own discoveryTimestamp, not rely on cr…
5d8d499
Select commit
Loading
Failed to load commit list.
StepSecurity Actions Security / StepSecurity Harden-Runner succeeded Apr 21, 2026 in 18s

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
governance.yaml 24700695332 1 2 View Insights
lint-pr.yaml 24700695326 1 2 View Insights

📚 Learn More

You can learn more about this GitHub check here

View more details on StepSecurity Actions Security