ci: use GitHub-hosted runners for public workflows - #129
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The runner label updates are consistent across workflows, and Blacksmith-specific configuration has been fully removed without impacting workflow structure.
Pull request overview
This PR updates the repository’s public GitHub Actions workflows to run exclusively on standard GitHub-hosted runners instead of paid Blacksmith runners, keeping the existing workflow structure (triggers, permissions, pins, and environments) intact.
Changes:
- Replaced Blacksmith Ubuntu runner labels with
ubuntu-24.04across CI and release verification jobs. - Replaced Blacksmith macOS runner labels with
macos-26for native Darwin verification and release jobs. - Removed the now-obsolete
.github/actionlint.yamlallowance that permittedblacksmith-*self-hosted runner labels.
File summaries
| File | Description |
|---|---|
| .github/workflows/release-slopmachine.yml | Switches verify/release jobs to GitHub-hosted Ubuntu 24.04 and macOS 26 runners. |
| .github/workflows/release-slopguard.yml | Switches verify, Darwin verify, and release jobs to GitHub-hosted Ubuntu 24.04 and macOS 26 runners. |
| .github/workflows/ci.yml | Switches all CI jobs previously using Blacksmith runners to GitHub-hosted Ubuntu 24.04 and macOS 26 runners. |
| .github/actionlint.yaml | Removes the Blacksmith-only runner-label allowance (file removed). |
Review details
- Files reviewed: 4/4 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.
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. |
Problem
This public repository's verification and release workflows select paid Blacksmith runners.
Solution
Move eight Linux jobs to standard GitHub-hosted Ubuntu 24.04 x64 and four native Darwin jobs to macOS 26 ARM64. Keep the existing verification, signing/notarization, triggers, permissions, action pins and release Environments. Remove the obsolete Blacksmith-only actionlint allowance.
The macOS mapping preserves the current OS and architecture: Blacksmith latest is macOS 26 ARM64, and GitHub offers standard macos-26 ARM64 runners.
Proof
Actionlint 1.7.12 and offline zizmor 1.29.0 passed (no findings; two existing first-party-ref suppressions). A comparison against main confirms the workflow files changed only at the twelve runner labels; the deleted linter config contained no other policy. Native verification will run in the existing PR lane. Signing/notarization and publication were not manually invoked.