Repository navigation
Keep peer ranges in sync and dedupe Yarn package updates - #134
Conversation
Restore the unchanged ncu command so caller dependency-section policy is not overridden. Synchronize tracking peers only when the new pin satisfies the old range; warn instead of crossing compatibility boundaries. Snapshot only the root and declared workspaces, tolerate BOMs and non-object sections, and retain symlink refusal. Cover the regressions while retaining Yarn dedupe and failure propagation.
|
Local checks passed on follow-up commit
These are the repository's native script gates; there is no application solution/build or separate integration lane. Local execution used macOS and Node 26.8.1. CI's Ubuntu environment and Node 22/24 configurations are CI-only because those Node versions are not installed locally. No live dependency-update or organization-wide write workflow was invoked. Release intent is The cross-provider review workflow (Opus 5.5 + GPT-6 Astra) passed on the pre-follow-up diff (round 4), with the confirmed minor finding addressed by |
Fixed
update-packagesworkflow now advance caret and tilde peer ranges that exactly track local pinned dependency versions when the new pin stays within the existing range; out-of-range updates leave the peer unchanged with a warning. (update-packages: ncu bump forks Yarn transitive resolutions and leaves peer ranges behind #110)yarn dedupeafter package updates to consolidate compatible transitive resolutions. (update-packages: ncu bump forks Yarn transitive resolutions and leaves peer ranges behind #110)