Found Node.js 20 deprecation issue causing CI failures on fork PRs — proposed fix

Community Development
,
1

Hi community! :waving_hand:

While working on my test coverage PRs, I noticed that
several CI workflows are failing on fork PRs due to
Node.js 20 deprecation.

What I found

The e2e-fork-pr.yml workflow uses actions that run on
Node.js 20 which GitHub is deprecating from June 2, 2026:

  • actions/checkout@v4
  • actions/setup-java@v4
  • actions/setup-node@v4
  • actions/github-script@v7

This is causing “Shared Build (Fork Rebuild)” to fail
on multiple PRs including #3194, #3248, #3077, #3208.

What I proposed

I opened issue #XXXX with a proposed fix to update
these actions to Node.js 24 compatible versions.

My question

Is this something contributors can work on?
I would love to submit a PR fixing this if
maintainers approve!

cc: @herbertyiga @mozzy11 @pmanko @Moses_Mutesasira

1 Like
2

@Rakesh I think this has been addressed, can we confirm if not , we can always create a new issue for it !

3

Hi @Agaba_Derrick_Junior → I had verified by checking the latest develop branch directly. The workflows still show:

  • actions/checkout@v4

  • actions/setup-java@v4

  • actions/cache@v4

The issue is not fixed yet. I already have a branch fix/github-actions-node24 ready with the updates. Should I go ahead and submit the PR?

4

PR has been submitted! You can find it here: #3403

I have also resolved the merge conflicts after rebasing against the latest develop. The PR is ready for review. :folded_hands: