Cirrus CI has ceased operations after the Cirrus Labs team moved to OpenAI.

Continuous Integration Service Cirrus CI stopped performing tasks 1 June 2026The decision is due to the fact that the team Cirrus Labs moves to OpenAI and joins the direction Agent InfrastructureCirrus Labs' official announcement stated that the company is no longer accepting new customers for Cirrus Runners, will support existing contracts until their expiration, and Cirrus CI itself will be shut down effective Monday, June 1, 2026.

Cirrus Labs operated for about nine years, developing tools for CI/CD, build environments, and virtualization. In 2018, the team launched a SaaS CI/CD service with support Linux, Windows и macOS, and later released Tart — a popular virtualization tool macOS on Apple Silicon, as well as Vetu и Orchard.

Who is affected?

On GitHub already tasks have appeared on migration in large open source projects. For example, runc opened the task "Migrate Cirrus CI jobs to GHA before June 1st" and directly indicated the need to move the tasks to GitHub Actions.

В Scipy The closure of Cirrus CI was linked to the risk of losing GPU runner tasks and noted that the project was not the only one in this situation.

У fish shell Cirrus CI was used for checks FreeBSD, Alpine, and older versions Ubuntu; without replacement, the project risked losing these CI runs.

The closure of Cirrus CI wasn't just the departure of another CI service from the market, but a significant event for the FOSS ecosystem. Projects that used Cirrus as more than just another tool were particularly hard hit. Linux-runner, but as a convenient platform for cross-platform builds, custom environments and macOS-virtualization.

What exactly is changing?

• Cirrus CI is closed.
  Repositories using .cirrus.yml can no longer rely on Cirrus CI to run tasks after June 1, 2026. This means projects will need to migrate their pipelines to GitHub Actions, GitLab CI, Buildkite, Jenkins, CircleCI, or another platform.

• Projects need to migrate CI manually.
  Closing Cirrus CI isn't just a matter of replacing one runner with another: .cirrus.yml configurations, images, build matrices, and platform checks will have to be migrated to the new CI system. This is especially important for projects that used Cirrus for non-standard environments, such as FreeBSD, Alpine, and older Ubuntu, GPU tasks or macOS-infrastructure.

• Cirrus Runners is no longer accepting new clients.
  The dedicated runner service is not closing for everyone at once, but new connections have been suspended, and existing clients will only be served until the end of their existing contracts.

• Tart, Vetu and Orchard are being migrated to a more permissive license.
  Cirrus Labs announced that its source-available tools, including Tart, Vetu, and Orchard, will be relicensed under a more permissive license, with royalties waived. This preserves the code for the community, but does not guarantee the same level of support from the original team.

Source: linux.org.ru