tailscale / tailscale/tailscale-rs
ci: create new crates as part of publish
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 61
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 22
Description
Currently, the CI publish flow assumes all crates in the workspace exist in crates.io, are assigned to the right owner accounts, and that trusted publishing is configured for them. This will not be true if new crates were created since the last publish; the publish flow should handle creating and configuring these.
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 CI publish flow and its current workspace-crate and crates.io configuration. Trace how existing crates are checked for ownership and trusted publishing, then define the equivalent handling for newly created crates. Done means the publish flow can create and configure new workspace crates before publishing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100