Can you please allow private npms to use trusted authentication with ci
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 712
- Forks
- 4.2k
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 3
Description
When having private modules until they get public the whole publish setup has to be done with a granular token, because trusted publishing is not possible with private packages. Although it may not be necessary it's makes it really hard to use. Also pnpm doesn't automatically pull in the latest npm makeing it not work except for node 24.
Contributor guide
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 by reading the documentation sections covering trusted publishing, private packages, and CI authentication. Check the current npm and pnpm behavior across the referenced Node versions. Done means the supported authentication path and private-package limitations are clearly documented, or the request is routed to the implementation project if documentation alone cannot address it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- authentication, ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100