Setup separate rustworkx-core publish job with trusted publishers#1630
Merged
Merged
Conversation
This commit splits out the release publish job for the rustworkx-core crate to crates.io from the wheels file into a separate job workflow file. This then lets us setup the cargo publish job to use the trusted publishers mechanism instead of a secret token for authentication which is more secure. The docs for using trusted publisher are located here: https://crates.io/docs/trusted-publishing the new cargo_publish workflow's job is updated to more closely follow the example in the docs. I've already updated the crate's configuration on crates.io to use cargo_publish.yml for the trusted publisher mechanism.
IvanIsCoding
approved these changes
Jul 9, 2026
IvanIsCoding
left a comment
IvanIsCoding
left a comment
Collaborator
There was a problem hiding this comment.
Awesome! I will let you authorize the workflow on the crates.io side. LGTM
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
Collaborator
|
@Mergifyio backport stable/0.18 |
Contributor
✅ Backports have been createdDetails
|
IvanIsCoding
pushed a commit
that referenced
this pull request
Jul 9, 2026
) (#1632) This commit splits out the release publish job for the rustworkx-core crate to crates.io from the wheels file into a separate job workflow file. This then lets us setup the cargo publish job to use the trusted publishers mechanism instead of a secret token for authentication which is more secure. The docs for using trusted publisher are located here: https://crates.io/docs/trusted-publishing the new cargo_publish workflow's job is updated to more closely follow the example in the docs. I've already updated the crate's configuration on crates.io to use cargo_publish.yml for the trusted publisher mechanism. (cherry picked from commit 70a4530) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 commit splits out the release publish job for the rustworkx-core crate to crates.io from the wheels file into a separate job workflow file. This then lets us setup the cargo publish job to use the trusted publishers mechanism instead of a secret token for authentication which is more secure. The docs for using trusted publisher are located here:
https://crates.io/docs/trusted-publishing
the new cargo_publish workflow's job is updated to more closely follow the example in the docs. I've already updated the crate's configuration on crates.io to use cargo_publish.yml for the trusted publisher mechanism.