automated release for public crates - #3455
Merged
Merged
Conversation
github-actions
Bot
added
the
S-waiting-on-review
syphar
changed the title
syphar
marked this pull request as ready for review
August 18, 2026 15:59
GuillaumeGomez
approved these changes
Aug 18, 2026
github-actions
Bot
added
S-waiting-on-deploy
syphar
removed
the
S-waiting-on-deploy
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.
see
rustwiderepoMy current idea for the first version is that we just tag the commit after we released, and then publish will be automatic. The tag can also be created by us manually doing a github release, as long as we follow the naming pattern.
In my plan, we'll have more in-tree public crates, like
cargo docs-rs(or some better CI builder)