Skip to content

ci: move workflows to GitHub-hosted runners - #4

Merged
loganlanou merged 1 commit into
mainfrom
ci/self-hosted-runner-targets
Jul 29, 2026
Merged

ci: move workflows to GitHub-hosted runners#4
loganlanou merged 1 commit into
mainfrom
ci/self-hosted-runner-targets

Conversation

@loganlanou

Copy link
Copy Markdown
Contributor

Problem

The self-hosted Prometheus x64 runner pool has been removed. Jobs in this repo
targeted [self-hosted, linux, x64, personal, prometheus], which now matches
zero runners — they queue indefinitely rather than failing, so the breakage is
silent.

Change

Retargets all jobs to ubuntu-latest.

Why GitHub-hosted rather than the ARM64 Mac runner pool

This is a public repository. Self-hosted runners on public repos allow a
pull request from a fork to execute arbitrary code on the runner host — GitHub
explicitly advises against the combination. Public repos stay on GitHub-hosted;
private repos keep using the self-hosted pool.

🤖 Generated with Claude Code

The self-hosted Prometheus x64 runner pool has been removed, leaving these
jobs with no matching runner - they queue indefinitely rather than fail.

Public repositories should not target self-hosted runners regardless: a pull
request from a fork can execute arbitrary code on the runner host. Retargets
all jobs to ubuntu-latest.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@loganlanou
loganlanou merged commit ed47c03 into main Jul 29, 2026
8 checks passed
@loganlanou
loganlanou deleted the ci/self-hosted-runner-targets branch July 30, 2026 13:43
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