Action failing with `ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER` when it was working before
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
The action was previously working fine (see this build which was built against glektarssza/webcraft@05cd8fedb7f03b07587ad79f1fe599f155b38f04).
As you can see from the above mentioned build/commit combination, the project has a package.json with a packageManager field.
I went to update pnpm this morning and the build has randomly started failing. See this build, the commit it was built against, and the package.json in that commit which has a packageManager field in the same format.
This is unexpected and confusing behaviour and quite likely a bug.
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
Start with the linked failing action run and compare it with the earlier successful run, then inspect the package.json files linked from each referenced commit, focusing on their packageManager fields. Reproduce the resolver error with the failing workflow; done means the action accepts the same packageManager format and the workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100