Currently the action is able to grab the version from the packageManager field which causes a few side effects.
If a user wants the repo to use a specified version of pnpm but not down to the patch level version, it was recommended to set the engines.pnpm field instead since packageManager does not support ranges.
It would be nice if the action supported reading this field as well.
Currently the action is able to grab the
version
from thepackageManager
field which causes a few side effects.If a user wants the repo to use a specified version of pnpm but not down to the patch level version, it was recommended to set the
engines.pnpm
field instead sincepackageManager
does not support ranges.It would be nice if the action supported reading this field as well.
Related: