Notice: FlyCI macOS runners will be discontinued effective September 30th, 2024.

Read more
See all blog posts

announcement

Discontinuing FlyCI macOS Runners - A New Chapter for FlyCI Wingman

Focus on FlyCI Wingman and Discontinue FlyCI macOS Runners

VRVeselina Radeva
An image representing the sunset of FlyCI macOS runners and the rise of FlyCI Wingman

To our valued FlyCI community,

A year ago, we grabbed the opportunity to provide fast, affordable, and up-to-date GitHub runners. Initially we started with Linux, but in late November we pivoted to macOS runners. In April, we launched a new feature - FlyCI Wingman, an AI assistant that helps developers debug and fix their failing GitHub workflows. FlyCI Wingman turned out to be a very compelling product idea in itself. This is why we decided to pivot and focus our efforts on improving FlyCI Wingman.

With this in mind, we have made the difficult decision to discontinue FlyCI macOS runners, effective September 30, 2024.

Why We're Making This Change

Through more than 20 customer interviews conducted from February till early April, we learned that debugging a failing GitHub workflow ranks highly among the most tedious and time-consuming tasks for developers. Various types of trivial failures demand their attention and consume their time. So, instead of focusing on what matters most, developers need to switch branches, do fixes, re-run workflows, and repeat paying the highest cost - their precious time.

Solving this problem became our mission.

What This Means for You

  • FlyCI macOS runners will be discontinued on September 30, 2024: After this date, the macOS runners will no longer be available or supported. You can review an example for migration to GitHub runners later in this post.

  • FlyCI Wingman will continue to receive all development focus: We continue investing in FlyCI Wingman, and you can expect ongoing improvements, new features, and enhanced support as we move forward.

We understand that this change may require adjustments to your workflows, and we are committed to making this transition as smooth as possible. Our support team is available to assist with any questions or concerns you may have regarding the change.

Migration to GitHub runners

There are different alternatives for the migration of your workflows. Below is a simple example of how to migrate to GitHub macOS runners.

jobs:
  test:
    name: My job
-   runs-on: flyci-macos-14-m2
+   runs-on: macos-14
    steps: ....

Moving Forward with FlyCI Wingman

FlyCI Wingman is designed to help developers fix their failing workflows in GitHub Actions. We are excited about the future of FlyCI Wingman and believe it will empower you to be more focused on the products you're building.

We encourage all users to try FlyCI Wingman. If you haven't explored it yet, now is the perfect time to see what FlyCI Wingman has to offer. See how to get started.

Thank You for Your Continued Support

We want to express our deepest gratitude to everyone who has used and supported FlyCI macOS runners over the last year. Your feedback and engagement have been invaluable, and we are excited to continue serving you through FlyCI Wingman.

As we enter this new chapter, our commitment to you remains as strong as ever. We are here to support you and look forward to continuing our journey together with FlyCI Wingman.

Sincerely,
The FlyCI Team

runners
wingman
flyci

Why choosing FlyCI Wingman?

Better focus

Shift your attention to innovating in your product instead of troubleshooting failing builds.

Save time

Automatically fix CI builds, reducing debugging time. FlyCI Wingman is doing the fixes for you.

Automated fixes

Automatically get fixes for failing GitHub Actions workflows directly proposed in your pull request.