Move node release workflow to use trusted publishing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
The tokens in the node workflow won't work anymore because npm has sunset the classic tokens.
https://github.blog/changelog/2025-12-09-npm-classic-tokens-revoked-session-based-auth-and-cli-token-management-now-available/
like used in https://github.com/mapbox/node-pre-gyp/blob/master/.github/workflows/release.yml#L91-L105
See migrations like:
https://github.com/maptiler/tileserver-gl/pull/1872
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 locating the node release workflow under .github/workflows and compare its token-based publishing steps with the linked node-pre-gyp workflow and migration example. Update the workflow to use trusted publishing, then verify that the release workflow no longer depends on classic npm tokens and still completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100