CI: Support automatic publish to crates.io on tag creation #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This would make it easier to release new crate, without having to ping anyone. Whoever has the right to create a new release on GitHub shall have the right to publish it to crates.io Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
|
cc @weihanglo |
|
cc @weihanglo Do you think it's something worth's having for jobserver-rs? cc-rs is already using this so that I don't have to ping someone on zulip to do the release every time 😂 |
|
Yeah, and we may want to standardize the release process to include changelog. Yet I think it's up to @petrochenkov who helps the release process a lot :) |
|
cc @Kobzol |
|
I don't have access to it. @jdno Could you please take a look? |
|
|
13 tasks
|
Thank you all! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
rust-lang/infra-team#117
This would make it easier to release new crate, without having to ping anyone.
Whoever has the right to create a new release on GitHub shall have the right to publish it to crates.io
NOTE that this new workflow requires a secret
CARGO_REGISTRY_TOKENto be set.With scoped token, you can limit the token to only have the ability to publish new version under name
jobserver, and nothing else.