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

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
Open
2 of 14 tasks
gdryke opened this issue Dec 5, 2024 · 26 comments · Fixed by rash-sh/rash#747, pando85/timer#242 or pando85/i3-auto-layout#95
Open
2 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-15 #11101

gdryke opened this issue Dec 5, 2024 · 26 comments · Fixed by rash-sh/rash#747, pando85/timer#242 or pando85/i3-auto-layout#95
Labels
Announcement

Comments

@gdryke
Copy link

gdryke commented Dec 5, 2024 •
edited by lkfortuna
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-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
@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
Merged
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
Merged
@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?

@gbraad gbraad mentioned this issue Jan 10, 2025
Merged
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Jan 10, 2025
@cfergeau
Revert "Update ubuntu runner to 'ubuntu-24.04'"
f88fbdf 
This reverts commit 2959505.
We prefer to stick with older ubuntu releases for building because of
containers#256
The issue with qemu with ubuntu 20.04 was fixed with
containers@fe7285a8a6a

Ubuntu 20.04 will be EOL'ed in April and the runner images will also go
away so we'll need to revisit this:
actions/runner-images#11101

Some options are to switch to Ubuntu 22.04 for our builds, or to look
into having pure go builds or statically linked builds, ...

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@cfergeau cfergeau mentioned this issue Jan 10, 2025
Merged
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Jan 10, 2025
@cfergeau
Revert "Update ubuntu runner to 'ubuntu-24.04'"
59ebb1c 
This reverts commit 2959505.
We prefer to stick with older ubuntu releases for building because of
containers#256
The issue with qemu with ubuntu 20.04 was fixed with
containers@fe7285a8a6a

Ubuntu 20.04 will be EOL'ed in April and the runner images will also go
away so we'll need to revisit this:
actions/runner-images#11101

Some options are to switch to Ubuntu 22.04 for our builds, or to look
into having pure go builds or statically linked builds, ...

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@kirawi kirawi mentioned this issue Jan 11, 2025
Merged
This was referenced Jan 11, 2025
Merged
Merged
Merged
@jpraynaud jpraynaud mentioned this issue Jan 13, 2025
Closed
12 tasks
rjeffman added a commit to rjeffman/ansible-freeipa that referenced this issue Jan 13, 2025
@rjeffman
upstream CI: Update runner images to Ubuntu 24.04
0fcc518 
Current upstream hosts use Ubuntu 20.04 images which will be fully
unsupported by 2025-04-01.

Update runners to use Ubuntu 24.04.

See: actions/runner-images#11101

Signed-off-by: Rafael Guterres Jeffman <rjeffman@redhat.com>
@rjeffman rjeffman mentioned this issue Jan 13, 2025
Closed
@erik-bershel erik-bershel mentioned this issue Jan 14, 2025
Merged
2 tasks
@tobtoht tobtoht mentioned this issue Jan 15, 2025
Merged
@dido18 dido18 mentioned this issue Jan 17, 2025
Closed
IvanNardi added a commit to IvanNardi/nDPI that referenced this issue Jan 17, 2025
@IvanNardi
CI: remove support for ubuntu-20.04
6900571 
This Ubuntu version is going to be deprecated.
See: actions/runner-images#11101
ajaust added a commit to ajaust/dlisio that referenced this issue May 27, 2025
@ajaust
amend! Update Ubuntu runners
06040cb 
Update Ubuntu runners

GitHub's Ubuntu 20.04 runners have been deprecated since 2025-05-14 [1].
The runners are updated to use the `ubuntu-latest` image.

[1]: actions/runner-images#11101
ajaust added a commit to ajaust/dlisio that referenced this issue May 27, 2025
@ajaust
amend! Update Ubuntu runners
8e64291 
Update Ubuntu runners

GitHub's Ubuntu 20.04 runners have been deprecated since 2025-05-14 [1].
The runners are updated to use the `ubuntu-latest` image.

[1]: actions/runner-images#11101
ClearlyEleanor pushed a commit to clearbank/clearbank.github.io that referenced this issue May 27, 2025
@cleareth @ClearlyEleanor
Docs fix: Update GitHub build version
2ee4278 
Update runner from deprecated ubuntu `20.04` to `ubuntu-latest` per: actions/runner-images#11101
@davidbmaier davidbmaier mentioned this issue May 27, 2025
Merged
@WebSpider WebSpider mentioned this issue May 27, 2025
Closed
unrooot added a commit to Quenty/rojo that referenced this issue May 27, 2025
@unrooot
ci: Fix linux build
0a90fab 
Needed to bump Ubuntu version in the workflow (see:
actions/runner-images#11101)
csharplus added a commit to mage-ai/mage-ai that referenced this issue May 28, 2025
@csharplus
[hw] Update the version of ubuntu to the latest to resolve the build …
3a8d1fe 
…issue with `trivy.yml` (#5783)

# Description
Resolve the issue that `trivy.yml` was not running, as discussed in
actions/runner-images#11101.

# How Has This Been Tested?
Updated to use the `ubuntu-latest` version, same with that in other
`yml` files for github actions.

# Checklist
- [ ] The PR is tagged with proper labels (bug, enhancement, feature,
documentation)
- [x] I have performed a self-review of my own code
- [ ] I have added unit tests that prove my fix is effective or that my
feature works
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation

cc:
<!-- Optionally mention someone to let them know about this pull request
-->
@wangxiaoyou1993
@jcotton42 jcotton42 mentioned this issue May 28, 2025
Merged
@Tiaansu Tiaansu mentioned this issue May 28, 2025
Open
@luthfifahlevi luthfifahlevi mentioned this issue May 28, 2025
Merged
This was referenced May 28, 2025
Open
Open
KevFan added a commit to KevFan/authorino that referenced this issue May 28, 2025
@KevFan
fix: use ubuntu-24.04 for image build action
6561c21 
Image build github action is broken as ubuntu-20.04 runner is deprecated and fully unsupported - actions/runner-images#11101

Signed-off-by: KevFan <chfan@redhat.com>
@KevFan KevFan mentioned this issue May 28, 2025
Merged
ajaust added a commit to ajaust/dlisio that referenced this issue May 28, 2025
@ajaust
Update Ubuntu runners
5ecca72 
GitHub's Ubuntu 20.04 runners have been deprecated since 2025-05-14 [1].
The runners are updated to use the `ubuntu-latest` image.

[1]: actions/runner-images#11101
@KevFan KevFan mentioned this issue May 28, 2025
Open
keshav-space added a commit to aboutcode-org/vulnerablecode that referenced this issue May 28, 2025
@keshav-space
Run release CI on Ubuntu 22.04
3c57bcd 
Ubuntu 20.04 runner is depricated actions/runner-images#11101

Signed-off-by: Keshav Priyadarshi <git@keshav.space>
@keshav-space keshav-space mentioned this issue May 28, 2025
Merged
abbyad added a commit to abbyad/abbyad.github.io that referenced this issue May 28, 2025
@abbyad
Fix unsupported ubuntu
d322efa 
As per actions/runner-images#11101
@satoren satoren mentioned this issue May 29, 2025
Merged
KevFan added a commit to KevFan/authorino that referenced this issue May 29, 2025
@KevFan
fix: use ubuntu-24.04 for image build action
dcab6ce 
Image build github action is broken as ubuntu-20.04 runner is deprecated and fully unsupported - actions/runner-images#11101

Signed-off-by: KevFan <chfan@redhat.com>
KevFan added a commit to KevFan/authorino that referenced this issue May 29, 2025
@KevFan
fix: use ubuntu-latest for image build action
5bd1356 
Image build github action is broken as ubuntu-20.04 runner is deprecated and fully unsupported - actions/runner-images#11101

Signed-off-by: KevFan <chfan@redhat.com>
lawrencedudley pushed a commit to lawrencedudley/micropython-esp32-pcnt that referenced this issue May 29, 2025
@dpgeorge @lawrencedudley
github/workflows: Stop using ubuntu-20.04.
b2e5720 
For GitHub Actions, ubuntu-20.04 is deprecated and will be removed by 1st
April 2025.  See announcement at
actions/runner-images#11101

This commit changes actions that use ubuntu-20.04 to a newer image.

Signed-off-by: Damien George <damien@micropython.org>
kaloyan-marinov pushed a commit to kaloyan-marinov/rename that referenced this issue May 29, 2025
5: react to the fact that the preceding commit caused GitHub Actions …
58173ba 
…to (not run the `workflow_run-test-suite` and) report the following:

```
jobs_run-test-suite
This is a scheduled Ubuntu 20.04 retirement. Ubuntu 20.04 LTS runner will be removed on 2025-04-15. For more details, see actions/runner-images#11101
```
0x676e67 added a commit to 0x676e67/boring2 that referenced this issue May 30, 2025
@0x676e67 @rushilmehra
@schien @ehaydenr @kornelski @semaj-cf @mstyura @nox
Sync upstream (#73)
a9da64c 
* Add fips-precompiled feature to support newer versions of FIPS (#338)

Newer versions of FIPS don't need any special casing in our bindings,
unlike the submoduled boringssl-fips. In addition, many users currently
use FIPS by precompiling BoringSSL with the proper build tools and
passing that in to the bindings.

Until we adopt the Update Stream pattern for FIPS, there are two main
use cases:

1. Passing an unmodified, precompiled FIPS validated version of
   boringssl (fips-precompiled)

2. Passing a custom source directory of boringssl meant to be linked
   with a FIPS validated bcm.o. This is mainly useful if you carry
   custom patches but still want to use a FIPS validated BoringCrypto.
   (fips-link-precompiled)

This commit introduces the `fips-precompiled` feature and removes the
`fips-no-compat` feature.

* Release 4.16.0 (#341)

* feat(x509): Implement `Clone` for `X509Store` (#339)


* boring(x509): impl Clone of X509Store

* expose SSL_set_compliance_policy

* fix clippy error

* Use ubuntu-latest for all ci jobs

ubuntu 20.04 is now deprecated:
actions/runner-images#11101

* add SslCurve::X25519_MLKEM768 constant

* Clippy

* Fix linking SystemFunction036 from advapi32 in Rust 1.87

* rustfmt ;(

* build: Fix the build for 32-bit Linux platform

* Update Cargo.toml

* boring(ssl): use `corresponds` macro in `add_certificate_compression_algorithm`

* Add `X509_STORE_CTX_get0_cert` interface

This method reliably retrieves the certificate the `X509_STORE_CTX` is
verifying, unlike `X509_STORE_CTX_get_current_cert`, which may return
the "problematic" cert when verification fails.

* Update bindgen from 0.70.1 -> 0.71.1.

* Revert "feat(x509): Implement `Clone` for `X509Store` (#339)" (#353)

* Revert "feat(x509): Implement `Clone` for `X509Store` (#339)"

This reverts commit 49a8d09.

See <cloudflare/boring#120>.

* Ensure Clone is not added to X509Store

* Add comment about why X509Store must not implement Clone

---------

Co-authored-by: Kornel <kornel@cloudflare.com>

* Release 4.17.0 (#354)

* Add set_verify_param

* clippy fix

---------

Co-authored-by: Rushil Mehra <84047965+rushilmehra@users.noreply.github.com>
Co-authored-by: Shih-Chiang Chien <shih-chiang@cloudflare.com>
Co-authored-by: Rushil Mehra <rmehra@cloudflare.com>
Co-authored-by: Eric Rosenberg <eric_rosenberg@apple.com>
Co-authored-by: Kornel <kornel@cloudflare.com>
Co-authored-by: James Larisch <jlarisch@cloudflare.com>
Co-authored-by: Yury Yarashevich <yura.yaroshevich@gmail.com>
Co-authored-by: Anthony Ramine <123095+nox@users.noreply.github.com>
0x676e67 added a commit to 0x676e67/boring2 that referenced this issue May 30, 2025
@0x676e67 @rushilmehra
@schien @ehaydenr @kornelski @semaj-cf @mstyura @nox
sync upstream (#74)
0f2461a 
* Add fips-precompiled feature to support newer versions of FIPS (#338)

Newer versions of FIPS don't need any special casing in our bindings,
unlike the submoduled boringssl-fips. In addition, many users currently
use FIPS by precompiling BoringSSL with the proper build tools and
passing that in to the bindings.

Until we adopt the Update Stream pattern for FIPS, there are two main
use cases:

1. Passing an unmodified, precompiled FIPS validated version of
   boringssl (fips-precompiled)

2. Passing a custom source directory of boringssl meant to be linked
   with a FIPS validated bcm.o. This is mainly useful if you carry
   custom patches but still want to use a FIPS validated BoringCrypto.
   (fips-link-precompiled)

This commit introduces the `fips-precompiled` feature and removes the
`fips-no-compat` feature.

* Release 4.16.0 (#341)

* feat(x509): Implement `Clone` for `X509Store` (#339)


* boring(x509): impl Clone of X509Store

* expose SSL_set_compliance_policy

* fix clippy error

* Use ubuntu-latest for all ci jobs

ubuntu 20.04 is now deprecated:
actions/runner-images#11101

* add SslCurve::X25519_MLKEM768 constant

* Clippy

* Fix linking SystemFunction036 from advapi32 in Rust 1.87

* rustfmt ;(

* build: Fix the build for 32-bit Linux platform

* Update Cargo.toml

* boring(ssl): use `corresponds` macro in `add_certificate_compression_algorithm`

* Add `X509_STORE_CTX_get0_cert` interface

This method reliably retrieves the certificate the `X509_STORE_CTX` is
verifying, unlike `X509_STORE_CTX_get_current_cert`, which may return
the "problematic" cert when verification fails.

* Update bindgen from 0.70.1 -> 0.71.1.

* Revert "feat(x509): Implement `Clone` for `X509Store` (#339)" (#353)

* Revert "feat(x509): Implement `Clone` for `X509Store` (#339)"

This reverts commit 49a8d09.

See <cloudflare/boring#120>.

* Ensure Clone is not added to X509Store

* Add comment about why X509Store must not implement Clone

---------

Co-authored-by: Kornel <kornel@cloudflare.com>

* Release 4.17.0 (#354)

* Add set_verify_param

* clippy fix

---------

Co-authored-by: Rushil Mehra <84047965+rushilmehra@users.noreply.github.com>
Co-authored-by: Shih-Chiang Chien <shih-chiang@cloudflare.com>
Co-authored-by: Rushil Mehra <rmehra@cloudflare.com>
Co-authored-by: Eric Rosenberg <eric_rosenberg@apple.com>
Co-authored-by: Kornel <kornel@cloudflare.com>
Co-authored-by: James Larisch <jlarisch@cloudflare.com>
Co-authored-by: Yury Yarashevich <yura.yaroshevich@gmail.com>
Co-authored-by: Anthony Ramine <123095+nox@users.noreply.github.com>
@sgoll sgoll mentioned this issue May 30, 2025
Merged
sgoll pushed a commit to HMIProject/open62541-sys that referenced this issue May 30, 2025
@uklotzde
Remove deprecated GitHub runners for Ubuntu 20.04 (#59)
14c8f9c 
This removes the Ubuntu 20.04 runners that have been
[deprecated](actions/runner-images#11101) from
our GitHub workflows.
@mmeest mmeest mentioned this issue May 30, 2025
Merged
@vohmar vohmar mentioned this issue May 30, 2025
Open
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