Conversation
| crates = ["libm"] | ||
| publish-workflow = "publish.yaml" | ||
| publish-environment = "publish" | ||
| teams = ["libs"] |
There was a problem hiding this comment.
libs team is an owner right now:
There was a problem hiding this comment.
What exactly does this key do by the way?
There was a problem hiding this comment.
It makes the libs team an owner of the crate on crates.io. Which means that they can still manually do yanks without going through an admin or CI (new versions are only deployable through CI though).
There was a problem hiding this comment.
Oh, does setting up trusted publishing here take over what's currently on crates.io? Meaning only rust-lang-owner and rust-lang/libs will have permissions?
(Which is fine, Jorge hasn't been involved in a while)
There was a problem hiding this comment.
I think we only sync team owners, not user owners.
| branches = ["main"] | ||
|
|
||
| [[crates-io]] | ||
| crates = ["libm"] |
There was a problem hiding this comment.
This is the only public crate of the repo. You can verify by running this script:
Dry-run check results |
4 participants
No description provided.