ci: use GitHub-hosted runners for verification - #18
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![slopzapper[bot]](https://avatars.githubusercontent.com/in/4527847?s=60&v=4){kind=small}
There was a problem hiding this comment.
🟢 Approval recommended
The changes cleanly migrate verification to GitHub-hosted runners and remove unused runner allowlisting with no remaining references to Blacksmith labels.
Pull request overview
This PR updates the repository’s CI verification workflow to run on standard GitHub-hosted runners (Ubuntu 24.04) instead of the previously configured Blacksmith runner labels, aligning the verification lane with the existing release workflow’s runner choice and removing now-obsolete actionlint configuration.
Changes:
- Switch
verifyjob runner fromblacksmith-2vcpu-ubuntu-2404toubuntu-24.04. - Remove the Blacksmith self-hosted runner label allowlist from
.github/actionlint.yaml.
File summaries
| File | Description |
|---|---|
| .github/workflows/verify.yml | Moves verification to GitHub-hosted Ubuntu 24.04 runner. |
| .github/actionlint.yaml | Removes Blacksmith runner label allowlist config that’s no longer needed. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Problem
Verification still uses Blacksmith in this public repository.
Solution
Run verification on standard GitHub-hosted Ubuntu 24.04, preserving Linux x64 and the existing verification/release graph. Remove the unused Blacksmith runner allowlist.