-
Notifications
You must be signed in to change notification settings - Fork 347
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
Update example-basic-pnpm.yml #1291
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,13 +21,17 @@ jobs: | |
# See https://github.com/pnpm/action-setup | ||
- name: Install pnpm | ||
uses: pnpm/action-setup@v4 | ||
# Optional when there is a `packageManager` field in the `package.json`. | ||
# See https://github.com/pnpm/action-setup?tab=readme-ov-file#version | ||
with: | ||
version: 9 | ||
|
||
# See https://github.com/actions/setup-node | ||
- name: Install Node.js | ||
uses: actions/setup-node@v4 | ||
with: | ||
# Note that pnpm `use-node-version` is not supported, yet | ||
# See https://github.com/actions/setup-node/issues/1130 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. actions/setup-node#1130 is an open enhancement request This isn't really the right place to be listing an enhancement request for an external action, when this isn't used in the example. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My point was to link to some place that explains that there is no way to set the node version based on the config that pnpm supports. I don't see a better place where this is documented. |
||
node-version: 20 | ||
cache: 'pnpm' | ||
cache-dependency-path: examples/basic-pnpm/pnpm-lock.yaml | ||
|
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.
https://nodejs.org/api/corepack.html lists this feature as experimental and not suitable for production.
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.
Interesting. However since the action has documentation on supporting it, they will still lookup the information from there, even if
packageManager
is not an official property anymore, right?