chore: upgrade pnpm to v11, bump deps - #914
Conversation
- Bump packageManager to pnpm@11.1.3 and regenerate lockfile - Migrate tsdown `external`/`inlineOnly` to `deps.neverBundle`/`onlyBundle` - pnpm v11 auto-added `minimumReleaseAgeExclude` entries to workspace yaml - Refresh dependency caret ranges to latest installed versions
|
|
commit: |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Summary
packageManagertopnpm@11.1.3and regeneratepnpm-lock.yamlunder pnpm v11.tsdown.config.tsfrom the deprecated top-levelexternal/inlineOnlyto the newdeps.neverBundle/deps.onlyBundleshape (clears build deprecation warnings).minimumReleaseAgeExcludeentries topnpm-workspace.yamlfor packages that had just landed within the trust-policy cutoff window.package.jsonandexamples/vite-vue3/package.jsonto the latest installed versions (eslint-config 7→9, typescript 5.9→6, vue-tsc 3.2→3.3, etc.).Test plan
pnpm installsucceeds under pnpm v11pnpm run build— noexternal/inlineOnlydeprecation warningspnpm run lint— cleanpnpm run typecheck— cleanpnpm run test— 36/36 passed