Update to npm OIDC publishing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, javascript, nodejs
Research direction
Start with .github/workflows/test-and-release.yml around line 65 and read the linked Node.js admin issue about npm OIDC publishing. Determine whether the repository is still active before choosing between updating publishing and archiving it. Done means the release workflow no longer relies on classic npm token publishing and the selected outcome is documented.
Written by the indexing model from the issue text.
Description
See https://github.com/nodejs/admin/issues/998. NPM classic token publishing will no longer be supported.
If this repo is no longer active, we could also archive this repo.
- Dominant language
- JavaScript
- Stars
- 33
- Forks
- 13
- Avg merge
- 9d 22h
- Merged PRs (30d)
- 1
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·