Skip to content

fix: switch CI from self-hosted to GitHub-hosted runners - #11

Merged
tallnato merged 1 commit into
mainfrom
paperclip/engino/NAT-63
Mar 26, 2026
Merged

fix: switch CI from self-hosted to GitHub-hosted runners#11
tallnato merged 1 commit into
mainfrom
paperclip/engino/NAT-63

Conversation

@tallnato

Copy link
Copy Markdown
Member

Summary

  • Replaced all runs-on: self-hosted with runs-on: ubuntu-latest in validate-pr.yml and deploy.yml
  • Replaced Homebrew Ruby setup (macOS-only brew --prefix ruby paths) with portable ruby/setup-ruby@v1 action with bundler-cache: true
  • No more Homebrew path references in Jekyll build steps

Why

Preparing the repo for open source (NAT-62). Self-hosted runners require internal infrastructure that external contributors won't have access to.

How to verify

  • Workflow YAML is valid
  • CI runs on ubuntu-latest runners
  • Jekyll build uses ruby/setup-ruby@v1 instead of Homebrew paths

🤖 Generated with Claude Code

Co-Authored-By: Paperclip noreply@paperclip.ing

Replace all `runs-on: self-hosted` with `runs-on: ubuntu-latest` in
validate-pr.yml and deploy.yml. Replace Homebrew Ruby setup with the
standard ruby/setup-ruby@v1 action with bundler-cache for portable
Jekyll builds on GitHub-hosted runners.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@tallnato
tallnato merged commit 7975c04 into main Mar 26, 2026
2 checks passed
@tallnato
tallnato deleted the paperclip/engino/NAT-63 branch March 26, 2026 10:02
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