Skip to content

no-issue: switch ubuntu-latest runners to warpbuild - #16

Closed
JeffTax wants to merge 1 commit into
mainfrom
chore/no-ref/warpbuild-runners
Closed

JeffTax wants to merge 1 commit into
mainfrom
chore/no-ref/warpbuild-runners

Conversation

@JeffTax

@JeffTax JeffTax commented Sep 28, 2026 •

Copy link
Copy Markdown

Summary

  • Replace runs-on: ubuntu-latest with runs-on: warp-ubuntu-latest-x64-2x in ci.yml so this repo's CI runs on WarpBuild, consistent with the rest of the kintsugi-tax org
  • Prompted by the org hitting 100% of its included GitHub Actions minutes for the billing cycle

Jira

N/A — chore/no-ref

Tests

No behavior change; CI on this PR validates the workflow still runs correctly on the new runner label

Document Checklist

N/A

🤖 Generated with Claude Code


Note

Low Risk
CI-only runner label swap with no application or release logic changes; main risk is WarpBuild availability or image differences vs GitHub-hosted runners.

Overview
Moves CI off GitHub-hosted ubuntu-latest to WarpBuild by setting runs-on: warp-ubuntu-latest-x64-2x on all four jobs in .github/workflows/ci.yml: lint-and-test, test-matrix, auto-tag, and release.

Steps, triggers, and job logic are unchanged; only the runner label changes so workflows align with other kintsugi-tax repos and reduce use of included GitHub Actions minutes.

Reviewed by Cursor Bugbot for commit aba0f48. Bugbot is set up for automated code reviews on this repo. Configure here.

The org has exhausted its included GitHub Actions minutes for the
billing cycle. Move this repo's CI onto WarpBuild runners to match
the convention already adopted across the rest of kintsugi-tax.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@JeffTax

JeffTax commented Sep 28, 2026

Copy link
Copy Markdown
Author

Closing — this is a public repo, and we're keeping the WarpBuild runner migration to internal/private repos only.

@JeffTax JeffTax closed this Sep 28, 2026
@JeffTax
JeffTax deleted the chore/no-ref/warpbuild-runners branch September 28, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant