Repository navigation
chore(ci): run CI on GitHub-hosted runners, drop Blacksmith - #346
Conversation
Public repo → GitHub-hosted runners (free for public repos). Blacksmith is retired org-wide. - ci.yml: blacksmith-2vcpu-ubuntu-2204 → ubuntu-22.04. release.yml (npm OIDC) already on ubuntu-latest, unchanged. 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 (1)
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. 📝 WalkthroughWalkthroughThe Bun, Node, and integration jobs in the CI workflow now run on GitHub-hosted ChangesCI runner update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The CI jobs now use GitHub-hosted Ubuntu 22.04 runners, with their setup and test commands unchanged. No actionable merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 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