You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: pnpm update --filter --latest should only change relevant packages and projects, with dedupe-peer-dependents=true (#8905)
* test(update): add failing tests for update with dedupe-peer-dependents=true
Relates to #8877
* fix: update --filter --latest should work with dedupe-peer-dependents
Fixes#8877, whereby
`update --filter --latest` with `dedupe-peer-dependents` would end up
updating all available dependencies for all projects.
* test(pnpm): more accurate dedupePeers filtered install case
* docs: add changeset for updateToLatest moving to projects/importers
* docs: add changesets for pnpm and plugin-commands-installation
* chore: fix tsc issue by removing unknown bound resolver property
This unknown property was accepted by tsc prior to adding updateToLatest
in toResovleImporter options, but now it was erroring out. This is
likely a tsc quirk about the shape of the object; regardless that
property is not defined, and should not be present.
* test: keep only pnpm/test/monorepo/dedupePeers.test.ts
There was duplicate coverage of the pnpm update --filter --latest
command between two tests, so this keeps only the one dedicated
to testing the dedupe-peer-dependents feature.
* chore: fix unused import error
`pnpm update --filter <pattern> --latest <pkg>` should only change the specified package for the specified workspace, when `dedupe-peer-dependents` is set to `true`[#8877](https://github.com/pnpm/pnpm/issues/8877).
0 commit comments