Configure trusted publishing for futures-rs#2594
Conversation
Dry-run check results |
| ] | ||
| publish-workflow = "publish.yml" | ||
| publish-environment = "publish" | ||
| teams = ["wg-async"] |
There was a problem hiding this comment.
Is this an approver? Since cramertj stopped being involved (5-6 years ago?) I'm the only current member of wg-async who has been involved in maintaining futures-rs, it seems odd that all wg members would have permission over releases.
There was a problem hiding this comment.
This specifies which team will own the crate on crates.io. But in practice with trusted publishing turned on, the only thing that this is useful for is yanking.
By the way, it would be great if the current active roster of wg-async was updated to match today's state!
There was a problem hiding this comment.
Technically these people have access to turn off trusted publishing and manually publish, but that would be a loud-ish action. Long-term I personally would like us to remove all human access to crates.io' (probably proxying yanks via some github/zulip bot) and/or have stronger yank-only enforcemeent.
| [environments.github-pages] | ||
|
|
||
| [environments.publish] | ||
| branches = ["main"] |
There was a problem hiding this comment.
| branches = ["main"] | |
| branches = ["0.3"] |
At this time, we don't create any release from main.
Discussed in https://rust-lang.zulipchat.com/#narrow/channel/187312-wg-async/topic/.E2.9C.94.20futures-rs.200.2E3.2E33.3F/with/611444229.