Migrated SDK workspace to pnpm (PLA-322) - #1041
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1041 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 30 30
Lines 3060 3060
Branches 459 459
=========================================
Hits 3060 3060 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
What changed
pnpm-lock.yamlminimumReleaseAge: 4320,strictDepBuilds: true, andblockExoticSubdeps: truetruebuild approvalsfrom-packagerelease flowWhy
This brings SDK onto the pnpm supply-chain baseline tracked by PLA-322 and makes dependency lifecycle execution reviewable and deny-by-default.
Validation
pnpm install --frozen-lockfilepnpm lintpnpm test(all 17 packages)pnpm buildpnpm publish --dry-run --no-git-checksfor all 17 packagesNPM_CONFIG_DRY_RUN=true pnpm ship:ciactionlintgit diff --checkThe exact Lerna publish dry-run completed successfully with no unpublished packages detected.