Add a CI workflow to publish new releases after a tag is pushed #71
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.
Context: rust-lang/infra-team#117
This repo has
write
access byt-compiler
andt-compiler-contributors
, and currently this workflow creates a release after a push of a tag or manually throughworkflow_dispatch
. If we don't want to give right to publish tot-compiler-contributors
, then we can remove theworkflow_dispatch
trigger, and create a branch protection to e.g.v-*
tags that would only allowt-compiler
to push.Requires a new secret
CARGO_REGISTRY_TOKEN
to be added to the secrets of this repository, which has scoped access to publishrustc-demangle
.