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
In my projects, I'm trying to specify exact versions of dependencies (including node and pnpm).
I would like to specify a version of pnpm once in package.json and reuse in pnpm/action-setup action
package.json has engines section for this
{
"engines": {
"pnpm": "7.32.5"
},
}
Would be great, if pnpm/action-setup could support this field.
Note: actions/setup-node supports engines.node via node-version-file property.
I'm also aware of packageManager property of package.json, but with it – I can't enforce exact version of PNPM, however with engines.pnpm + engine-strict=true - I can, so everyone in the team has same environment
In my projects, I'm trying to specify exact versions of dependencies (including
node
andpnpm
).I would like to specify a version of
pnpm
once inpackage.json
and reuse inpnpm/action-setup
actionpackage.json
hasengines
section for thisWould be great, if
pnpm/action-setup
could support this field.Note:
actions/setup-node
supportsengines.node
vianode-version-file
property.I'm also aware of
packageManager
property ofpackage.json
, but with it – I can't enforce exact version of PNPM, however withengines.pnpm
+engine-strict=true
- I can, so everyone in the team has same environmentIt might be related to this: #24
The text was updated successfully, but these errors were encountered: