Skip to content

Migrate CI from Cirrus CI to GitHub Actions#447

Draft
fkorotkov-oai wants to merge 1 commit into
mainfrom
dev/fkorotkov/migrate-ci-to-github-actions
Draft

Migrate CI from Cirrus CI to GitHub Actions#447
fkorotkov-oai wants to merge 1 commit into
mainfrom
dev/fkorotkov/migrate-ci-to-github-actions

Conversation

@fkorotkov-oai
Copy link
Copy Markdown
Collaborator

What changed

  • replace Cirrus CI lint, Linux, macOS, and release jobs with GitHub Actions
  • keep GoReleaser binary releases and multi-architecture Docker image publishing
  • remove nfpm/Fury publishing and obsolete system-package assets
  • build the container directly with Go instead of installing GoReleaser Pro in the Dockerfile
  • publish the image as ghcr.io/openai/orchard and source Vetu from openai/vetu in Linux CI

Release setup

Before the next release, configure GORELEASER_KEY, GH_PAT, and the existing macOS signing/notarization values as repository secrets. GH_PAT needs write access to cirruslabs/homebrew-cli.

Validation

  • actionlint
  • goreleaser check --soft with GoReleaser Pro 2.16.0
  • go test ./... passed outside hardware-dependent integration packages

The local hardware integration tests could not register an Orchard worker because ioreg is unavailable in this execution environment; the migrated macOS job runs them on the Tahoe runner.

@fkorotkov-oai fkorotkov-oai requested a review from edi-oai June 5, 2026 17:14
@fkorotkov-oai fkorotkov-oai force-pushed the dev/fkorotkov/migrate-ci-to-github-actions branch from ad5cd25 to 262d469 Compare June 5, 2026 17:20
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