buildx's pnpm version doesn't match other actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, github-actions
- Domain
- build-system, ci-cd
Research direction
Start with pull-request.yml and trace the build and push action that runs npm install -g pnpm. Compare its pnpm installation with the pinned pnpm/action-setup@v3 step, then verify the build uses the same pnpm version and no longer shows the inconsistent supply-chain policy behavior.
Written by the indexing model from the issue text.
Description
When pull-request.yml contains
- name: Setup pnpm
uses: pnpm/action-setup@v3
with:
version: 9
The build and push action still installed an unpinned pnpm version. Not actually sure what it is since only npm is logged, but the ci had different behavior than local as a result (CI did the supply chain policy check when local didn't)
[44](https://github.com/satisfactorymodding/Documentation/actions/runs/26487807585/job/77998977322#step:6:250)
#13 [build 3/8] RUN npm install -g pnpm
#13 1.313
#13 1.313 added 1 package in 1s
#13 1.313
#13 1.314 1 package is looking for funding
#13 1.314 run `npm fund` for details
#13 1.316 npm notice
#13 1.316 npm notice New minor version of npm available! 11.13.0 -> 11.15.0
#13 1.316 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.15.0
#13 1.316 npm notice To update run: npm install -g npm@11.15.0
#13 1.316 npm notice
#13 DONE 1.4s
#16 [build 6/8] RUN pnpm install
#16 0.907 ? Verifying lockfile against supply-chain policies (499 entries)...
#16 2.594 ✗ Lockfile failed supply-chain policy check (499 entries in 1.6s)
- Dominant language
- Python
- Stars
- 28
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
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.
More from satisfactorymodding/Documentation
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
satisfactorymodding/Documentation#406 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
All issues in satisfactorymodding/Documentation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100