ci: migrate from Cirrus to GitHub Actions - #7061
Draft
ShortDevelopment wants to merge 2 commits into
Draft
Conversation
Update actions
ShortDevelopment
force-pushed
the
ci/macos-github-actions
branch
from
August 19, 2026 17:33
4e18197 to
13627b0
Compare
ShortDevelopment
force-pushed
the
ci/macos-github-actions
branch
from
August 19, 2026 17:49
13627b0 to
612375d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Cirrus CI has shut down on June 1, 2026 (Source).
Solution
Like PostgreSQL, we could move to GitHub Actions.
This PR is a POC of how this might look like.
Even though I heard rumors about bad performance and outages of GitHub Actions
See Standard GitHub-hosted runners for public repositories
Alternatives
We could ask other providers with OSS programs.
That might give us better ci performance...
@rhuanjl What do you think?
Fixes #7060