Skip to content

ci: run on GitHub-hosted runners - #1

Merged
bsommers merged 1 commit into
mainfrom
ci/github-hosted-runners
Nov 8, 2026
Merged

bsommers merged 1 commit into
mainfrom
ci/github-hosted-runners

Conversation

@bsommers

@bsommers bsommers commented Nov 8, 2026

Copy link
Copy Markdown
Owner

Switches both CI jobs from the self-hosted KVM runner ([self-hosted, linux, vm]) to ubuntu-24.04.

  • Standard GitHub-hosted runners are free with no minute limit in public repositories (billing docs).
  • The self-hosted VM is meant for private repos only: its runners are persistent and the guest can reach the host network.
  • Timeouts go up (25 to 60 min, and 15 to 45 min) because a cold-cache stack build is slower on a hosted runner.

The fork-PR guard and permissions: contents: read are unchanged. Fork PRs from outside contributors also need approval (repo setting all_external_contributors).

This PR's own CI run is the test that the hosted runner has everything the jobs need.

🤖 Generated with Claude Code

The repo is public, so standard GitHub-hosted runners are free with no
minute limit. The self-hosted KVM runner is for private repos only (its
runners are persistent and it can reach the host network).

Timeouts are raised because a cold-cache stack build on a hosted runner
is slower than on the warm VM.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bsommers
bsommers merged commit 27db3f6 into main Nov 8, 2026
2 checks passed
@bsommers
bsommers deleted the ci/github-hosted-runners branch November 8, 2026 21:08
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