GitHub Actions runner breaking changes announced

To whom it may concern,

GitHub announced breaking changes to their runner fleet in this post: Notice of upcoming deprecations and breaking changes in GitHub Actions runners - GitHub Changelog

Summary:

  • Deprecation of macos-12, upgrade MacOS runners to macos-14
  • No more arm64 Ubuntu images, use Arm-supplied images
  • People using upload-artifact actions should check, that they don’t rely on auto-inclusion of hidden files / folders
1 Like

GitHub announced some breaking changes to their GitHub Actions services: Notice of upcoming deprecations and changes in GitHub Actions services - GitHub Changelog

Summary:

  • Reduced Webhook rate limit in GitHub Actions to 1250 incoming requests per 10 seconds
  • GitHub Action actions/cache will drop V1 & V2, use V3 or V4

Thanks, I will make PRs for the macos change.

1 Like

@vaeng can you self-merge like fix: update macOs workflow by vaeng · Pull Request #298 · exercism/ballerina · GitHub?

1 Like

GitHub announced more breaking changes to their GitHub Actions services:

GitHub announced more breaking changes to their GitHub Actions services:

  • ubuntu-latest will change to Ubuntu 24.04 starting on December 5, 2024 and ending on January 17, 2025
  • Actions workflows will stop running automatically for PRs from forks, when any commit author in the PR is untrusted (currently, all commit authors are trusted, when the PR is created by a trusted account)
  • There are changes announced to the GitHub Actions hosting workflow, which I think do not affect track maintainers but may affect Exercism providing workflows for tracks / infrastructure
2 Likes

We’ve been pinning to specific versions where possible so I don’t think this should be a big concern. After doing a quick GitHub search, yamlscript/.github/workflows/test.yml at 084ef73555c07a5235b852cefb89581638965254 · exercism/yamlscript · GitHub is the only ubuntu-latest I found for an active track.

And that’s probably “just going to work” as it’s using a container argument there, and the calls find and make have been stable since forever.

1 Like

GitHub will phase out Ubuntu 20.04 Runner images soon. Use Ubuntu 24.04 now.

Also the switch to “immutable actions” goes on. I think this does not affect track maintainers but may affect Exercism providing workflows for tracks / infrastructure.

1 Like

Ubuntu 24 has been LTS since april. Please update your actions if you have not done so yet.

Inexperienced maintainer here. We have this in our actions:

os: [ubuntu-22.04, windows-2022, macos-14]

I think they’re still LTS. Do we need to change them?

1 Like

They are still supported and will be for quite a while. Now that 24 has become part of long term support, upgrading to that when you have nothing else to do will save you from having to do it later, possibly at a moment where there’s a lot going on.

2 Likes

These have ubuntu-20.04

cobol/.github/workflows/test.yml
red/.github/workflows/ci.yml

elixir-test-runner/.github/workflows/elixir_tests.yml
fsharp-test-runner/.github/workflows/test.yml
1 Like

Thanks!

@ErikSchierboom wanna update them test runners?
@axtens / @kapitaali are you maintaining Cobol still?
@loziniak could you have a look at Red?

I haven’t been a Red maintainer for a few weeks now, but see Upgrade CI to Ubuntu 24 by BNAndras · Pull Request #197 · exercism/red · GitHub.

1 Like

I’m happy to approve and merge PR’S.

2 Likes

The Windows CI fails because the actions/cache workflow it uses is deprecated as well.

1 Like

I haven’t been that active but can do some things. However, I haven’t touched the actions workflow at all and wouldn’t know what to do about it.

1 Like

@BNAndras knows what to do i think. If you can approve and merge the PR once it turns green (passes), that’d be great.

The long story short is that the running image and it’s dependencies are old. Often this is the only change required but sometimes we find that in new versions other things also don’t work.

1 Like

I’m in Hungary this week visiting family, but I can take a look next week. The GitHub guidance is pretty in depth so I can probably figure it out then.

4 Likes