Mergeable app cannot be enforced after upgrade to node v20

[horia-stoenescu]

Hello,

After doing this upgrade for node version to v20: #738, mergeable app stopped working as it could not read anymore configuration from .github/mergeable.yml.

Also, I cannot see this github app in my status checks for branch protection rules: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks#checks anymore 😞 .

Is there anyone else who saw this kind of issue after the upgrade?

Thank,
Horia

[davidalbers]

I'm having issues after the upgrade as well, I can still see the app in the status checks but it never reports success or failure.

[horia-stoenescu]

I'm having issues after the upgrade as well, I can still see the app in the status checks but it never reports success or failure.

Yes, same for me. And after removing it from status checks, I could not add it back.

[horia-stoenescu]

What I've managed to do as a workaround for now:

• clone mergeable repository
• get reset --hard HEAD~1 # to return to previous working state
• start deploy of mergeable self hosted using steps from here: https://github.com/mergeability/mergeable/blob/master/deploy.md

[shine2lay]

I'll try to revert it back to last known working build

[horia-stoenescu]

I'll try to revert it back to last known working build

It seems now that it's solved, thanks a lot 😁 . New commits in PRs are able to trigger this check for Mergeable.
Also, it can be enabled as required in branch protection rules.

Is there a planned hotfix for this upgrade to node v20?
I am asking in order to make sure that no such issues will appear in the near future.

Thank you,
Horia

[andekande]

Ho exactly did you upgrade?
The referenced PR just bumbed node version in the ci-cd pipeline because some tools required that.
That's different from the runtime the bot is hosted with. In Dockerfile its still on 18.