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
Currently, manypkg check and manypkg fix decide to resolve dependency versions based on the most commonly witnessed range in the repo. -- Only when there are equal quantities of each range specifier do we select the highest range:
I also prefer this behavior and would be happy to help.
I do worry, though, that y'all are trying to avoid introducing unnecessary configuration... if so is there another recommended way to upgrade a dependency accross an entire monorepo to a specified range?
Currently,
manypkg check
andmanypkg fix
decide to resolve dependency versions based on the most commonly witnessed range in the repo. -- Only when there are equal quantities of each range specifier do we select the highest range:manypkg/packages/cli/src/checks/utils.ts
Lines 152 to 158 in b8b9144
Would we support a flag
--use-highest-range
on each command to force this algorithm to select the highest range for a given dependency?Alternative: add a
.manypkg.config.json
this and other flags?I'm happy to contribute this code change if a maintainer can indicate if they'd accept an appropriate PR implementing this.
The text was updated successfully, but these errors were encountered: