chore(devdeps): update pnpm to v10.5.0 #2471
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.2.1->10.5.0Release Notes
pnpm/pnpm (pnpm)
v10.5.0Compare Source
Minor Changes
Allow to set the "pnpm" settings from
package.jsonvia thepnpm-workspace.yamlfile #9121.Added support for automatically syncing files of injected workspace packages after
pnpm run#9081. Use thesync-injected-deps-after-scriptssetting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a.npmrcfile at the root of the workspace. Example:The
packagesfield inpnpm-workspace.yamlbecame optional.Patch Changes
pnpm linkwith no parameters should work as if--globalis specified #9151.--config.prefix such as--@​scope:registry=https://scope.example.com/npm#9089.pnpm link <path>should calculate relative path from the root of the workspace directory #9132.pnpm-lock.yamlfile when using--fix-lockfileand--filter. #8639v10.4.1Compare Source
Patch Changes
--allow-buildoption overlaps with thepnpm.ignoredBuildDependencieslist #9105.init-package-managershould work.v10.4.0Compare Source
Minor Changes
pnpm approve-builds --globalworks now for allowing dependencies of globally installed packages to run postinstall scripts.The
pnpm addcommand now supports a new flag,--allow-build, which allows building the specified dependencies. For instance, if you want to install a package calledbundlethat hasesbuildas a dependency and want to allowesbuildto run postinstall scripts, you can run:This will run
esbuild's postinstall script and also add it to thepnpm.onlyBuiltDependenciesfield ofpackage.json. So,esbuildwill always be allowed to run its scripts in the future.Related PR: #9086.
The
pnpm initcommand adds apackageManagerfield with the current version of pnpm CLI #9069. To disable this behaviour, set theinit-package-managersetting tofalse.Patch Changes
pnpm approve-buildsshould work after two consecutivepnpm installruns #9083.packageManagercannot start withv.v10.3.0Compare Source
Minor Changes
strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #9071.Patch Changes
verify-deps-before-runafterpnpm install --production|--no-optional#9019.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.