[feature request] Use version of pnpm specified in package.json's engines section
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
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
It might be related to this: https://github.com/pnpm/action-setup/issues/24
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the pnpm/action-setup entry point and the related issue #24, then inspect how package.json is handled. Confirm the requested engines.pnpm value can be read and reused as the pnpm version, including the exact 7.32.5 example, without breaking existing setup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100