Update Node.js version to 24 in action.yml#124
Closed
lgrosales wants to merge 1 commit intodigitalocean:v2from
Closed
Update Node.js version to 24 in action.yml#124lgrosales wants to merge 1 commit intodigitalocean:v2from
lgrosales wants to merge 1 commit intodigitalocean:v2from
Conversation
|
👍 this needs pulled in NodeJS 20 is EOL in ~30 days. |
|
Any news here? |
|
bump |
|
@andrewsomething bump please! |
Author
|
@DO-rrao would you be able to help us with this PR please? |
3 tasks
Author
|
Closing as the new PR linked addressed this issue and got approved already. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
runs.using: node24) to stay compatible as GitHub Actions removes support for Node 20.npm run packageoutput is unchanged.Testing
npm run test(fails: npm could not write logs to/Users/leo/.npm/_logs; eslint reportsno-unused-varsinmain.jslines 78, 92, 137). This was already present and will address in a follow up PR.