Migrate NPM publishing to to Trusted Publishing
- Dominant language
- TypeScript
- Stars
- 270
- Forks
- 193
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 36
Description
## Enhancement Request
NPM tokens now expire after 90 days and an expired token blocked the most recent release. We should move the project to Trusted Publishing (uses an OIDC login instead and automates the inclusion of provenance). This will require updates to the release workflow - however, FINOS tell us that any necessary setup on their end has already been done.
The token has just been renewed and will be good until early July, we should migrate the project before it expires again.
### Additional Information
See: https://docs.npmjs.com/trusted-publishers
Contributor guide
Research direction
Start by locating the release workflow and read the npm Trusted Publishers documentation linked in the issue. Update the workflow to use OIDC-based Trusted Publishing instead of an expiring npm token, including provenance, then verify that a release can publish successfully without the token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100