Repository navigation
[MNT]: ci: ubuntu-20.04 GitHub Actions runner will soon be unmaintained #29766
Description
Summary
The ubuntu-20.04 GitHub Actions runner image, currently used in the tests.yml workflow will soon be unsupported, as notified at: actions/runner-images#11101
Proposed fix
Ubuntu 20.04 itself is a long-term-support release, however it is also nearing the end of that support cycle, and will no longer be supported by Canonical from May 2025: https://ubuntu.com/20-04
I'd suggest removing the ubuntu-20.04 jobs from the tests.yml workflows at the end of this month (March 2025).
Activity
timhoffm commentedon Mar 18, 2025
Thanks for the reminder.
We have two runners with ubuntu-20.04:
matplotlib/.github/workflows/tests.yml
Lines 60 to 61 in 3edda65
Per our policy, we're supporting minor Python versions that are released in the last 42 months. For Python 3.10 this means we can officially drop support on Apr. 10. Given that I don't think we'll release until then, I'm ok with simply removing this job, even though we formally have a short untested period for 3.10.
matplotlib/.github/workflows/tests.yml
Lines 50 to 52 in 3edda65
We still want a min-version check. This should be moved to ubuntu-22.04 and python 3.11.
jayaddison commentedon Mar 18, 2025
That job does seem to test one or two other factors: disabling link-time optimization, and something to do with
matplotlib-inline. Perhaps I could try updating it to useubuntu-22.04(or evenubuntu-24.04) instead, to continue to exercise those?timhoffm commentedon Mar 18, 2025
You're right. This does more and shouldn't be removed without replacement.
matplotlib-inline: The backend mapping was moved from IPython to matplotlib, see #27948. The test ensures that newer matplotlib versions still work with older ipython. This specific addition is tremporary, but I agree that it's too early to drop it. However, it's in a similar spirit as "Minimum versions", I therefore suggest to move this intorequirements/testing/minver.txtand test it with that job.The no-lto can be moved to the regular python 3.11 job.
tacaswell commentedon Mar 18, 2025
Normally we don't backport CI changes, but given that these jobs are going away we should drag this back to atleast the 3.10.x branch.
tacaswell commentedon Mar 18, 2025
On second thought, we can not just straight backport it as we still should test py3.10 on mpl3.10.x