Skip to content

ci: run workflows on Blacksmith runners - #661

Merged
deanq merged 3 commits into
mainfrom
ci/blacksmith-runners
Oct 30, 2026
Merged

deanq merged 3 commits into
mainfrom
ci/blacksmith-runners

Conversation

@justinwlin

@justinwlin justinwlin commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

The runpod org now has an IP allow list, and GitHub-hosted runners are outside it. Any job that calls the GitHub API from them fails with the runpod organization has an IP allow list enabled, even with the default GITHUB_TOKEN. This moves every job to blacksmith-2vcpu-ubuntu-2404, the label runpod/main-ui and runpod/runpod-assistant already use.

The PyPI jobs in cd.yml (test-publish, pypi-publish) run on runpod-4vCPU-ubuntu-2404 instead, the org's GitHub-hosted runner with static, allow-listed IPs. Trusted publishing only accepts GitHub-hosted runners, and Blacksmith counts as self-hosted. A probe job on this branch confirmed the runner accepts jobs from this repo. The label is literal because the org variable RUNNER_4VCPU_UBUNTU_2404 isn't shared with this repo.

@deanq deanq left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed: runner labels only, all moved to allowlisted runners (Blacksmith, plus runpod-4vCPU-ubuntu-2404 for trusted publishing). A tag probe in #664 confirmed GITHUB_TOKEN can tag the 2.0.0 release commit, so this unblocks the 2.0.0 release.

@deanq
deanq merged commit a4ba078 into main Oct 30, 2026
9 checks passed
@deanq
deanq deleted the ci/blacksmith-runners branch October 30, 2026 20:55
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.

2 participants