actions/node-versions
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 509 Wiki Activity

[versions-manifest] Update for release from 07/19/2024 #182

Merged
github-actions[bot] merged 1 commits from update-versions-manifest-file into main 2024-07-22 15:17:51 +05:00
Conversation 13 Commits 1 Files Changed 1 +43
github-actions[bot] commented 2024-07-19 20:49:09 +05:00 (Migrated from github.com)
Copy Link

Update versions-manifest.json for release from 07/19/2024

Update versions-manifest.json for release from 07/19/2024
👍 20 👀 4 ❤️ 1 🚀 11
MikeMcC399 commented 2024-07-19 21:06:54 +05:00 (Migrated from github.com)
Copy Link

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!
👍 11
jsumners commented 2024-07-20 16:09:46 +05:00 (Migrated from github.com)
Copy Link

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?
👍 12
RobinTail commented 2024-07-20 17:49:43 +05:00 (Migrated from github.com)
Copy Link

@HarithaVattikuti || @aparnajyothi-y || @priya-kinthali || @priyagupta108, please merge

@HarithaVattikuti || @aparnajyothi-y || @priya-kinthali || @priyagupta108, please merge
👍 4
LitoMore (Migrated from github.com) approved these changes 2024-07-21 15:56:13 +05:00
RobinTail (Migrated from github.com) approved these changes 2024-07-21 20:55:12 +05:00
RobinTail (Migrated from github.com) left a comment
Copy Link

I heard if it's approved 255 times then it will be merged automatically without involving code owners :)

I heard if it's approved 255 times then it will be merged automatically without involving code owners :)
LitoMore commented 2024-07-21 21:05:50 +05:00 (Migrated from github.com)
Copy Link

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.
👍 2
torokati44 (Migrated from github.com) approved these changes 2024-07-21 21:20:45 +05:00
torokati44 commented 2024-07-21 21:21:06 +05:00 (Migrated from github.com)
Copy Link

Can't hurt to try... 🙄

Can't hurt to try... 🙄
👎 5
Standard8 commented 2024-07-21 21:49:11 +05:00 (Migrated from github.com)
Copy Link

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.
👍 4 😆 2
priya-kinthali (Migrated from github.com) approved these changes 2024-07-22 09:59:50 +05:00
priyagupta108 (Migrated from github.com) approved these changes 2024-07-22 10:26:58 +05:00
aparnajyothi-y (Migrated from github.com) approved these changes 2024-07-22 13:06:03 +05:00
RobinTail commented 2024-07-22 14:45:12 +05:00 (Migrated from github.com)
Copy Link

What is that thing that's currently keeping you from merging it, @priya-kinthali && @priyagupta108 && @aparnajyothi-y ?

What is that thing that's currently keeping you from merging it, @priya-kinthali && @priyagupta108 && @aparnajyothi-y ?
👍 2 👎 1
Sign in to join this conversation.
Reviewers
No Reviewers
LitoMore
RobinTail
torokati44
priya-kinthali
priyagupta108
aparnajyothi-y
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shaman
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: actions/node-versions#182
Delete Branch "update-versions-manifest-file"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?