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

Add Node.js 20.11.0 #162

Closed
karlhorky wants to merge 1 commits from patch-1 into main
pull from: patch-1
merge into: actions:main
Conversation 1 Commits 1 Files Changed 1 +4
karlhorky commented 2024-01-12 21:44:19 +05:00 (Migrated from github.com)
Copy Link

Since there is no way to open issues here, I opened a PR for discussion instead.

Node.js 20.11.0 has been out since 10 Jan 2024, but the automated PRs have not yet updated this.

Maybe some automation is broken here? Or is there a schedule for releasing these new versions? If it is scheduled, maybe the delay from the release to the manifest being updated could be decreased?

I'm coming here because of a failure in actions/setup-node to resolve lts/* to 20.11.0, also when using check-latest: true:

Run actions/setup-node@v4
  with:
    node-version: lts/*
    always-auth: false
    check-latest: false
    token: ***
Attempt to resolve LTS alias from manifest...
Found in cache @ /opt/hostedtoolcache/node/20.10.0/x64
Environment details
  node: v20.10.0
  npm: 10.2.3
  yarn: 1.22.21

cc @MaksimZhukov @dmitry-shibanov @dusan-trickovic

Since there is no way to open issues here, I opened a PR for discussion instead. [Node.js 20.11.0](https://nodejs.org/en/blog/release/v20.11.0) has been out since 10 Jan 2024, but the automated PRs have not yet updated this. Maybe some automation is broken here? Or is there a schedule for releasing these new versions? If it is scheduled, maybe the delay from the release to the manifest being updated could be decreased? I'm coming here because of [a failure in `actions/setup-node` to resolve `lts/*` to `20.11.0`](https://github.com/actions/setup-node/issues/940), also when using `check-latest: true`: ``` Run actions/setup-node@v4 with: node-version: lts/* always-auth: false check-latest: false token: *** Attempt to resolve LTS alias from manifest... Found in cache @ /opt/hostedtoolcache/node/20.10.0/x64 Environment details node: v20.10.0 npm: 10.2.3 yarn: 1.22.21 ``` cc @MaksimZhukov @dmitry-shibanov @dusan-trickovic
👍 1
karlhorky commented 2024-01-26 14:21:01 +05:00 (Migrated from github.com)
Copy Link

LTS alias is now properly resolving Node.js 20.11.0:

Attempt to resolve LTS alias from manifest...
Found in cache @ /opt/hostedtoolcache/node/20.11.0/x64

As per the comment from @HarithaVattikuti:

Closing.

LTS alias is now properly resolving Node.js 20.11.0: ``` Attempt to resolve LTS alias from manifest... Found in cache @ /opt/hostedtoolcache/node/20.11.0/x64 ``` As per the comment from @HarithaVattikuti: - https://github.com/actions/setup-node/issues/940#issuecomment-1911104358 Closing.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
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#162
Delete Branch "patch-1"

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?