Conversation
The CI Standard Checks workflow has been timing out after 24 hours since March 27. The reusable workflow defaults to ci-base-scale-set (self-hosted runners), which are restricted to private repos. This change explicitly specifies ubuntu-latest (GitHub-hosted runners) for this public repository. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ Security Analysis ResultsGreat news! No security issues found in this pull request. Analysis Summary:
Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page |
|
This PR is missing a Jira ticket reference in the title or description. |
|
🥷 Code experts: No results found No code experts were identified for the files in this pull request based on git blame analysis. This may occur when:
If you expected to see expert suggestions, consider:
To learn more about /:\gitStream - Visit our Docs |
|
|
[BOT] Preview available with hash |



Fix CI Standard Checks timeout due to runner restrictions
Problem
CI Standard Checks workflow has been timing out after 24 hours since March 27. The reusable workflow defaults to
ci-base-scale-set(self-hosted runners), but these are restricted to private repos. Public repos likeembedcan't access them, causing jobs to queue indefinitely until auto-cancelled.Solution
Override the runner parameter to explicitly use
ubuntu-latest(GitHub-hosted runners).Changes
.github/workflows/ci-standard-checks.ymlto specifyrunner: ubuntu-latestImpact