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

**URL:** https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261
**Category:** Development
**Tags:** dev\_setup, dev
**Created:** [April 1, 2026, 11:16pm UTC](https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261 "2026-04-01T23:16:34Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Rakesh](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/rakesh/32/1213_2.png) [@Rakesh](https://talk.openelis-global.org/u/Rakesh)
#### Post date: [April 1, 2026, 11:16pm UTC](https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261/1 "2026-04-01T23:16:34Z")

</div>

Hi community! 👋

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

---

<div class="post-metadata">

### Author: ![Agaba\_Derrick\_Junior](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/agaba_derrick_junior/32/503_2.png) [@Agaba\_Derrick\_Junior](https://talk.openelis-global.org/u/Agaba_Derrick_Junior)
#### Post date: [April 9, 2026, 4:23pm UTC](https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261/2 "2026-04-09T16:23:58Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Rakesh](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/rakesh/32/1213_2.png) [@Rakesh](https://talk.openelis-global.org/u/Rakesh)
#### Post date: [April 11, 2026, 7:45am UTC](https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261/3 "2026-04-11T07:45:37Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![Rakesh](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/rakesh/32/1213_2.png) [@Rakesh](https://talk.openelis-global.org/u/Rakesh)
#### Post date: [April 11, 2026, 8:10am UTC](https://talk.openelis-global.org/t/found-node-js-20-deprecation-issue-causing-ci-failures-on-fork-prs-proposed-fix/2261/4 "2026-04-11T08:10:05Z")

</div>

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