Repository navigation
chore(ci): run CI on GitHub-hosted runners, drop Blacksmith - #163
Conversation
Public repo → GitHub-hosted runners (free for public repos). Blacksmith is retired org-wide.
- Every workflow: blacksmith-{2,4}vcpu-ubuntu-2404 → ubuntu-latest (PyPI trusted publishing needs GitHub-hosted anyway).
- CLAUDE.md: runner line updated to match.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (5)
Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughCI and publishing workflow jobs now use ChangesWorkflow updates
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to No actionable release or CI issue is established; the change is mergeable after normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Org rule (2026-10-07): private repos run CI on Ubicloud standard runners, public repos on GitHub-hosted runners; Blacksmith is retired.
Public repo → GitHub-hosted runners (free for public repos). Blacksmith is retired org-wide.
The checks on this PR run on the new runners — they are the proof.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit