Repository navigation
Migrate package manager from npm to pnpm #19
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
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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -20,23 +20,26 @@ jobs: | |||||||||
| - name: Checkout | ||||||||||
| uses: actions/checkout@v6 | ||||||||||
|
|
||||||||||
| - name: Setup pnpm | ||||||||||
| uses: pnpm/action-setup@v4 | ||||||||||
|
||||||||||
| uses: pnpm/action-setup@v4 | |
| uses: pnpm/action-setup@v4 | |
| with: | |
| version: 10.33.0 |
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.
The workflow sets up pnpm via pnpm/action-setup@v4 but doesn’t pin the pnpm version. Since package.json now pins pnpm via the packageManager field (pnpm@10.33.0) and pnpm-lock.yaml is lockfileVersion 9 (pnpm 10), CI should explicitly install that version (or enable Corepack and rely on packageManager) to avoid accidental breakage if the action’s default changes.