-
Notifications
You must be signed in to change notification settings - Fork 0
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 cache examples, update to latest actions #3
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@karlhorky Thanks for the pull request!
Overall LGTM, but I've left some reviews. Can you take a look?
Co-authored-by: Masafumi Koba <[email protected]>
Co-authored-by: Masafumi Koba <[email protected]>
From the docs: https://github.com/nvm-sh/nvm#:~:text=In%20place%20of,version%20of%20node > In place of a version pointer like "14.7" or "16.3" or "12.22.1", you can use the following special default aliases with `nvm install`, `nvm use`, `nvm run`, `nvm exec`, `nvm which`, etc: > > - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)
We have to update https://github.com/ybiquitous/using-nvm-on-github-action/pull/3/checks#step:11:8 |
Maybe, pnpm v8 dropped support for Node.js v14: I upgraded to v20.16.0 (latest LTS) in this commit: Since new versions of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thank you 😄 👍🏼
Glad to help :) Thanks for the guidance, review and merge! |
Closes #2