Deprecation of Ubuntu 20.04 and introduction of Ubuntu 24.04 as the new default starting February 23

[helinanever]

To ensure that builds on Codemagic run with the highest level of reliability and security, we are deprecating Linux build machines running Ubuntu 20.04.

Starting February 23, 2026, build machines running Ubuntu 20.04 will be removed from the pool, and Ubuntu 24.04 will become the new default for Linux builds.

Up until the end-of-life (EOL) date for Ubuntu 20.04, we will be conducting several brownouts, during which builds will fail for users who have explicitly set this Ubuntu version in their codemagic.yaml.

Please read on to learn how this change may affect you and how to migrate.

Codemagic.yaml users

You are affected by this change if your workflow is configured to use the linux_x2 or linux_x4 instance type.

If your workflow explicitly specifies 20.04 as the Ubuntu version, your builds will fail during the brownouts and after the default machines are switched. See the brownout schedule below. We recommend upgrading the Ubuntu version in your workflows to 24.04 as soon as possible to avoid disruptions.

environment:
  ubuntu: 24.04

If your workflow does not specify an Ubuntu version, your builds run on the default Linux machine. There will be no changes to your builds during the brownouts. However, starting from February 23, 2026, Linux builds will run on Ubuntu 24.04 by default.

Please note that you may need to make additional changes to your workflow if your builds rely on older versions of pre-installed software. We recommend comparing the Linux machine specifications in our documentation.

Flutter Workflow Editor users

Linux builds in the Flutter Workflow Editor always use the default Linux machine type. Currently, there is no option to select a specific Ubuntu version.

Your builds will continue to run on Ubuntu 20.04 machines until the default is switched. There will be no changes during the brownouts. Once Ubuntu 24.04 becomes the new default, all Linux builds will automatically run on that version.

Please note that you may need to make additional changes to your workflow if your builds rely on older versions of pre-installed software. We recommend comparing the Linux machine specifications in our documentation.

Brownout schedule and EOL

• February 9, 2026 – 08:00 to 16:00 UTC (8 hours)
• February 11, 2026 – 00:00 to 16:00 UTC (16 hours)
• February 17, 2026 – 06:00 to 22:00 UTC (16 hours)
• February 19, 2026 – 00:00 to 24:00 UTC (24 hours)
• February 23, 2026 – Deprecated machines become unavailable and Ubuntu 24.04 becomes the new default

If you have any questions or concerns, please contact our customer support via the in-app chat widget.

[dineralex]

Flutter drive integration tests not working on linux machine from today (works as expected on mac), looks like chomedriver is missing, there is no informative log.

[Becca-Saka]

Hello @dineralex

Looks like you are right, both chrome and chromedriver are missing from the machine. I have raised this with the team but just so you are not blocked while this is resolved, can you add this step to install them?

      - name: Install Chrome + ChromeDriver
        script: |
          set -e

          # Install Chrome 
          wget -q https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
          sudo apt-get install -y ./google-chrome-stable_current_amd64.deb

          
          CHROME_VERSION=$(google-chrome --version | grep -oP '[\d.]+' | head -1)
          echo "Chrome version: $CHROME_VERSION"

          # Download matching ChromeDriver
          wget -q "https://storage.googleapis.com/chrome-for-testing-public/${CHROME_VERSION}/linux64/chromedriver-linux64.zip"
          unzip chromedriver-linux64.zip
          sudo mv chromedriver-linux64/chromedriver /usr/local/bin/chromedriver
          sudo chmod +x /usr/local/bin/chromedriver