axodotdev / axodotdev/cargo-dist

Support for npm trusted publishing

Open
#2,403 1 comment 2 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2.1k
Forks
149
Avg merge
1d 11h
Merged PRs (30d)
32

Description

It would be nice to be able to enable "Trusted Publisher" and be able to use an alternative npm publishing workflow that handles doing trusted publishing to avoid needing to keep a NPM_TOKEN in the repository

Theres examples of how to implement trusted publishers here:
https://docs.npmjs.com/trusted-publishers

Enabling trusted publishers does require that the package exists first so it would likely need to exist alongside the existing npm publishing workflow as a option that can be turned on to switch between the versions.

Thanks for your consideration

Contributor guide

Open the contributing guide

Research direction

Read the npm trusted publishing documentation linked in the issue, then locate cargo-dist's existing npm publishing workflow and the option that controls it. Compare the current NPM_TOKEN-based path with the requested trusted-publisher path; done means users can select the alternative workflow while retaining the existing option.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, node.js
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.