You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The Ubuntu 20.04 Actions runner image will begin deprecation on 2025-02-01 and will be fully unsupported by 2025-04-15 #11101
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
Reacted by lin72h, Nando cru, Michael Klishin, Marko Kaznovac, Ариф Мамиев Валех оглы, Alexander Fallenstedt, Rosalie Wanders, Gernot Steinegger, kim.jaejun, Udit8348 and 37 more
Reacted by Bulat Khasanov, Alison Monteiro, nameless, Tilak Madichetti, Mickael Bourgois, 云云朮, Markos Gogoulos, paulbourelly999, God-damnit-all, jgauthi and 12 more
Reacted by Mustapha BARKI
Reacted by Mustapha BARKI
Reacted by Mustapha BARKI
Reacted by Michael Klishin, Yatabib1 and Mustapha BARKI
Reacted by Sanaei, Yatabib1, fenjenkan, Israel Fernandes, Siim Sams, An Long, Luca Bertelli, Anisur Rahman, Vic Thor, randymcmillan and 1 more
Could you please use ISO standard for dates. It is not clear what this is 2025-04-01 - April or Jan?
Reacted by Ариф Мамиев Валех оглы, Amritpal-Nijjar, Stefan kyre, DeGloria, Roman Pavliuk, richard-whitehead2, Scrub, Bruno Pereira, Mohamed Wael, Alexander Zhuravlev and 8 more
Reacted by ANB5 Development, samleonard, Mahesh Bandara Wijerathna, Kyle White, Anish Senathi, Michael Skinner, Toby Allen, olivroy, Giancarlos Castillo, scul86 and 81 more
Reacted by ANB5 Development, Mahesh Bandara Wijerathna, Charles Song, Oriol Janés, David Weikersdorfer, cyan, Richard Li, RehabFakhryGibreel, Elian NEPPEL, Myeong-geun Shin and 18 more
Reacted by Gerard Braad | RGRV, iBug, Josh Soref, Valentin Vuk, Gabriel Cocenza, Martin Kjellstrand, Thierry D., Tim Hasler, intrigus-lgtm, Etaash Mathamsetty and 88 more
Reacted by Lukasz Stolarczuk, Daniel Hensby, Nick Viera, Mahesh Bandara Wijerathna, Jeff McKenna, maciektr, The Tumultuous Unicorn Of Darkness, Maciej Brencz, Clayton O'Neill, Adrian Pop and 2 more
This does not #10721
The confusion is real. It should not be a puzzle for a community to decipher the public announcements.
Reacted by Anton Bessonov, Anan and Agustín Núñez Arenas
Reacted by David Weikersdorfer, theo, uzlonewolf, tamirse, garyschulte, nicolas-castro92, Adrian Pop, raphop, Sebastian Wojtczak, Johnson Page and 6 more
Reacted by Aspen James, cyan, Xavi Fortes and Maciej Brencz
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?
Reacted by YukiOnishi0024, Duo Xu, arohter and Pedro Ribeiro
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.
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.
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?
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.
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.
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.
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?
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.
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.
Activity
Prepare ubuntu 24 github action update
AlexSkrypnyk commentedon Dec 16, 2024
Could you please use ISO standard for dates. It is not clear what this is 2025-04-01 - April or Jan?
rtiangha commentedon Dec 17, 2024
That is ISO 8601.
https://www.iso.org/iso-8601-date-and-time-format.html
AlexSkrypnyk commentedon Dec 17, 2024
This does not #10721
The confusion is real. It should not be a puzzle for a community to decipher the public announcements.
rtiangha commentedon Dec 17, 2024
Then maybe post the ISO complaint under the right issue? The dates in this issue's description are correct.
Use Ubuntu 20.04 for coverage
lonex-branch commentedon Jan 9, 2025
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/runnerproject, to what point we need to start worrying about the OS version of the self-hosted runner that requires a needed upgrade?Revert "Update ubuntu runner to 'ubuntu-24.04'"
Revert "Update ubuntu runner to 'ubuntu-24.04'"
upstream CI: Update runner images to Ubuntu 24.04
CI: remove support for ubuntu-20.04
CI: remove support for ubuntu-20.04
CI: remove support for ubuntu-20.04
181 remaining items
chore: move test runners to ubuntu-latest
chore: move test runners to ubuntu-22.04
Fix validation workflow (PR #1417)
ad-m-ss commentedon Feb 27, 2025
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.
kalyan-gavini-epam commentedon Mar 4, 2025
As a temporary measure, we (
DevOps team) have updated the image toUbuntu 22.04for 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.
jonGigPig commentedon Mar 5, 2025
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
jsloan117 commentedon Mar 5, 2025
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?
gdryke commentedon Mar 28, 2025
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 for2025-04-01 13:00-21:00 UTCand2025-04-08 13:00-21:00 UTC.These brownout dates will impact both GitHub Actions and Azure DevOps images.
KFo3 commentedon Apr 14, 2025
Do we have a time frame for the 15th? When we officially deprecate 20.04?
SlySven commentedon Apr 15, 2025
Be aware that if you are building AppImages using the
linuxdeployqttool 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
gdryke commentedon Apr 15, 2025
The standard
ubuntu-20.04is 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.
AnonymousScript007 commentedon Apr 24, 2025
Hello
osseonews commentedon May 2, 2025
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?
akabarki76 commentedon Jun 2, 2025
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.
RFOF-NETWORK commentedon Jun 11, 2025
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.