chore: Update to pnpm v8#5476
chore: Update to pnpm v8#5476lachlancollins merged 6 commits intoTanStack:mainfrom lachlancollins:pnpm-v8
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit ff710b8. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|
@TkDodo I spoke too soon - codesandbox doesn't use pnpm 8 yet. If I allow it to regen the pnpm lockfile it works, which isn't necessary for github actions. I don't quite understand why codesandbox hasn't been throwing errors since it's been using lockfile v6.0 for a while! EDIT: Fixed by using corepack |
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #5476 +/- ##
==========================================
+ Coverage 91.79% 92.23% +0.43%
==========================================
Files 101 112 +11
Lines 3889 4276 +387
Branches 974 1116 +142
==========================================
+ Hits 3570 3944 +374
- Misses 298 311 +13
Partials 21 21
☔ View full report in Codecov by Sentry. |
2 participants
The main branch is already using lockfile version 6.0 (pnpm v8), while the alpha branch has lockfile version 5.4 (pnpm v7). Can't think of any reason against updating (see changes here), and it should mean github actions run faster since it doesn't need to regenerate the lockfile back to 5.4.