Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Node.js 20.11.0 #162

Closed
wants to merge 1 commit into from
Closed

Add Node.js 20.11.0 #162

wants to merge 1 commit into from

Conversation

karlhorky
Copy link

@karlhorky karlhorky commented Jan 12, 2024

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

@karlhorky
Copy link
Author

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.

@karlhorky karlhorky closed this Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant