-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] Use version of pnpm specified in package.json's engines section #84
Comments
For anyone interested, as a workaround, I'm doing this right now - name: Get PNPM version from package.json
id: pnpm-version
shell: bash
run: echo "pnpm_version=$(node -p 'require(`./package.json`).engines.pnpm')" >> $GITHUB_OUTPUT
- name: Install PNPM
uses: pnpm/[email protected]
with:
version: ${{ steps.pnpm-version.outputs.pnpm_version }} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: