Add API token support to endpoints for managing Trusted Publishing configurations #11926
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new
trusted-publishing
endpoint scope to our API tokens. If this scope is used, then the API token can be used to create, list and delete Trusted Publishing configurations for the configured crates. As with the other scopes, a legacy token without any scopes can also be used for the same purpose now.This change will allow our users with larger workspaces to automate the setup of creating Trusted Publishing configurations, which should help with adoption of Trusted Publishing by power users.