Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
3 of 14 tasks
gdryke opened this issue Dec 5, 2024 · 5 comments
Open
3 of 14 tasks

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

gdryke opened this issue Dec 5, 2024 · 5 comments
Labels
Announcement

Comments

@gdryke
Copy link

gdryke commented Dec 5, 2024 •
edited
Loading

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-01.

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::

  • To be updated in place here, before 2025-02-01 (brownouts will not start immediately)

Target date

2025-04-01

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
@erik-bershel erik-bershel pinned this issue Dec 5, 2024
@Kichura Kichura mentioned this issue Dec 5, 2024
Merged
ChillerDragon added a commit to ChillerDragon/ddnet that referenced this issue Dec 10, 2024
@ChillerDragon
Prepare ubuntu 24 github action update
96e4da4 
simplify build action by removing cmake path which is no longer needed

ubuntu-latest will slowly become ubuntu 24 actions/runner-images#10636
and ubuntu-20 will be deprecated actions/runner-images#11101
@badlop badlop mentioned this issue Dec 11, 2024
Open
@AlexSkrypnyk
Copy link

AlexSkrypnyk commented Dec 16, 2024 •
edited
Loading

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

@rtiangha
Copy link

That is ISO 8601.

https://www.iso.org/iso-8601-date-and-time-format.html

@AlexSkrypnyk
Copy link

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

@rtiangha
Copy link

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

@kevemueller kevemueller mentioned this issue Dec 17, 2024
Open
This was referenced Jan 7, 2025
Open
Merged
2-towns referenced this issue in codex-storage/nim-codex Jan 9, 2025
@2-towns
Use Ubuntu 20.04 for coverage
b5848da
@veaceslavdoina veaceslavdoina mentioned this issue Jan 9, 2025
Open
@lonex-branch
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Announcement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@AlexSkrypnyk @rtiangha @gdryke @lonex-branch