Skip to content

The Ubuntu 20.04 Actions runner image will begin deprecation on 2025-02-01 and will be fully unsupported by 2025-04-15 #11101

Closed

Description

@gdryke

Breaking changes

We will soon start the deprecation process for Ubuntu 20.04. While the image is being deprecated, you may experience longer queue times during peak usage hours. Deprecation will begin on 2025-02-01 and the image will be fully unsupported by 2025-04-15.

To raise awareness of the upcoming removal, we will temporarily fail jobs using Ubuntu 20.04. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:

GitHub Actions\Azure DevOps::

  • March 4 14:00 UTC – 22:00 UTC
  • March 11 13:00 UTC – 21:00 UTC
  • March 18 13:00 UTC – 21:00 UTC
  • March 25 13:00 UTC – 21:00 UTC
  • April 1 13:00 UTC – 21:00 UTC
  • April 8 13:00 UTC – 21:00 UTC

Target date

2025-04-01
2025-04-15

The motivation for the changes

We maintain the latest two stable versions of any given OS version. Ubuntu 24.04 is going GA on 2025-02-01 so we start deprecating the oldest image at that time.

Possible impact

Workflows using the ubuntu-20.04 image label should be updated to ubuntu-latest, ubuntu-22.04, ubuntu-24.04 .

Platforms affected

  • Azure DevOps
  • GitHub Actions

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022

Mitigation ways

N/A

Activity

  1. pinned this issue on Dec 5, 2024
  2. AlexSkrypnyk commented on Dec 16, 2024

    @AlexSkrypnyk

    Could you please use ISO standard for dates. It is not clear what this is 2025-04-01 - April or Jan?

  3. rtiangha commented on Dec 17, 2024

    @rtiangha
  4. AlexSkrypnyk commented on Dec 17, 2024

    @AlexSkrypnyk

    This does not #10721
    The confusion is real. It should not be a puzzle for a community to decipher the public announcements.

  5. rtiangha commented on Dec 17, 2024

    @rtiangha

    Then maybe post the ISO complaint under the right issue? The dates in this issue's description are correct.

  6. added a commit that references this issue on Jan 9, 2025
  7. lonex-branch commented on Jan 9, 2025

    @lonex-branch

    I assume this only affects GitHub-hosted runner. Can i ask a related question about ubuntu 20.04 upgrade to the self-hosted runner? As long as we keep our runner API by integrating the latest release from the actions/runner project, to what point we need to start worrying about the OS version of the self-hosted runner that requires a needed upgrade?

  8. 181 remaining items

  9. added a commit that references this issue on Feb 25, 2025
  10. ad-m-ss commented on Feb 27, 2025

    @ad-m-ss

    Is there a way to make Dependabot do pull requests with such updates? We don't need to wait for deprecation to do updates, but it's hard to remember that we should do. The upgrade for us was smooth as we run everything in Docker anyway, but we would prefer to control & review updates for tracking purposes.

  11. kalyan-gavini-epam commented on Mar 4, 2025

    @kalyan-gavini-epam

    As a temporary measure, we (DevOps team) have updated the image to Ubuntu 22.04 for the Ubuntu_20.04_2019 and ubuntu_20.04_platform runners. Consequently, we kindly request that you update the workflows utilizing these two runners to use ubuntu-latest, ubuntu-22.04, or ubuntu-24.04 as appropriate.
    Please note that we will be phasing out the 20.04 runners in the near future.

  12. jonGigPig commented on Mar 5, 2025

    @jonGigPig

    It is now 9:03 GMT on the 5th March. I am getting the brownout error. See image. What is going on? I thought the brownout times were as follows:

    March 4 14:00 UTC – 22:00 UTC
    March 11 13:00 UTC – 21:00 UTC
    March 18 13:00 UTC – 21:00 UTC
    March 25 13:00 UTC – 21:00 UTC

    Image

  13. jsloan117 commented on Mar 5, 2025

    @jsloan117

    Does this mean the code base for generating an Ubuntu 20.04 image from this repo will also be removed on 04-01-2025? If not, when is the planned date for that?

  14. gdryke commented on Mar 28, 2025

    @gdryke
    Author

    We've made the decision to postpone the Ubuntu 20.04 image deprecation by two weeks. The Ubuntu 20.04 image will now be fully deprecated on 2025-04-15, with two additional brownouts scheduled for 2025-04-01 13:00-21:00 UTC and 2025-04-08 13:00-21:00 UTC.

    These brownout dates will impact both GitHub Actions and Azure DevOps images.

  15. KFo3 commented on Apr 14, 2025

    @KFo3

    Do we have a time frame for the 15th? When we officially deprecate 20.04?

  16. SlySven commented on Apr 15, 2025

    @SlySven

    Be aware that if you are building AppImages using the linuxdeployqt tool then you are really out of luck for the moment as it won't run in the Ubuntu 22.04 LTS runner - the maintainer of that tool insists that you use the oldest supported Ubuntu LTS instance and since 20.04 does not officially reach EOL until next month he won't update the tool to match the later libc (I think it is) until (at least) then.

    probonopd/linuxdeployqt#630

  17. gdryke commented on Apr 15, 2025

    @gdryke
    Author

    Do we have a time frame for the 15th? When we officially deprecate 20.04?

    The standard ubuntu-20.04 is already off, larger runners using the ubuntu-20.04 image will be breaking over the course of the day.

    As for the questions on self-hosted runner support, Ubuntu 20.04 will remain supported for the Actions agent. Watch the GitHub changelog for announcements on any upcoming deprecations, it's usually tied to dotnet or node versions losing support on the given OS, so it will be a longer time horizon than this image deprecation.

  18. AnonymousScript007 commented on Apr 24, 2025

    @AnonymousScript007

    Hello

  19. osseonews commented on May 2, 2025

    @osseonews

    You do realize that this upgrade has entirely made Github Codespaces useless because packages that rely on Github actions now are using the latest unbuntu, which requires a hire GLIBC library and if you try to run any of these packages on Codespaces you get an error that the GLIBC is not found, so you are stuck and can't code on Codespaces because you don't have control over the OS on codespaces. So Github broke their own Codespaces platform? See this for example: cloudflare/workers-sdk#7911 - We can't run any of our Cloudflare applications on Codespaces anymore as they all throw the GLIBC error as workered builds from GitHub actions and requires the higher version of ubuntu but codespaces doesn't?

  20. akabarki76 commented on Jun 2, 2025

    @akabarki76

    deprecation of Ubuntu 20.04 for GitHub Actions and Azure DevOps runners. The transition to Ubuntu 22.04 and 24.04 is underway, with brownout periods scheduled to alert users before full support ends on April 15, 2025.

    If you're using Ubuntu 20.04 in your workflows, it’s a good time to update your runner configurations to avoid disruptions. You might want to:

    Switch to ubuntu-latest, ubuntu-22.04, or ubuntu-24.04 for future compatibility.

    Test your workflows with newer versions to ensure seamless transitions.

    Review dependencies that could be affected by the upgrade.

  21. RFOF-NETWORK commented on Jun 11, 2025

    @RFOF-NETWORK

    Image why is your systim still having struggles with my image handling/scaling? When I can help to resolve this problem .....;-->) no problem! Let us talk about your V Codes kreation &/or-> algorytmen.

    PS:
    How you can seeing in my (... in this diskussion ...) on my picture is there an specific Error. @github is meaning/ your (@gdryke ) konstruktion to scale every image algos/ecos is not enough for an 100% succes workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions