Any workflow specifying node-version: 22 in actions/setup-node currently fails in GitHub Actions with
npm error Exit handler never called!
- Please expedite! See https://github.com/actions/setup-node/issues/1112 and [Node.js v22.5.1](https://github.com/nodejs/node/releases/tag/v22.5.1) release notes.
Any workflow specifying `node-version: 22` in `actions/setup-node` currently fails in GitHub Actions with
> npm error Exit handler never called!
I appreciate that the action is pulling from your own infrastructure so as not to blow up someone else's, but this whole process really needs to be more automated and immediate. Why does this need to wait on a human to intervene? Why wasn't this manifest update part of the PR that added 22.5.1 to the releases list? When are we going to be able to run our CI jobs that utilize 22.x again?
I appreciate that the action is pulling from your own infrastructure so as not to blow up someone else's, but this whole process really needs to be more automated and immediate. Why does this need to wait on a human to intervene? Why wasn't this manifest update part of the PR that added 22.5.1 to the releases list? When are we going to be able to run our CI jobs that utilize 22.x again?
I heard if it's approved 255 times then it will be merged automatically without involving code owners :)
@RobinTail Please do not spread false information.
> I heard if it's approved 255 times then it will be merged automatically without involving code owners :)
@RobinTail Please do not spread false information.
Please do not, it unnecessary spams everyone that is following this issue, wasting everyone's time. Please refrain from commenting, and be patient until a one of the maintainers are available.
Please do not, it unnecessary spams everyone that is following this issue, wasting everyone's time. Please refrain from commenting, and be patient until a one of the maintainers are available.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Update versions-manifest.json for release from 07/19/2024
Any workflow specifying
node-version: 22inactions/setup-nodecurrently fails in GitHub Actions withI appreciate that the action is pulling from your own infrastructure so as not to blow up someone else's, but this whole process really needs to be more automated and immediate. Why does this need to wait on a human to intervene? Why wasn't this manifest update part of the PR that added 22.5.1 to the releases list? When are we going to be able to run our CI jobs that utilize 22.x again?
@HarithaVattikuti || @aparnajyothi-y || @priya-kinthali || @priyagupta108, please merge
I heard if it's approved 255 times then it will be merged automatically without involving code owners :)
@RobinTail Please do not spread false information.
Can't hurt to try... 🙄
Please do not, it unnecessary spams everyone that is following this issue, wasting everyone's time. Please refrain from commenting, and be patient until a one of the maintainers are available.
What is that thing that's currently keeping you from merging it, @priya-kinthali && @priyagupta108 && @aparnajyothi-y ?