Reorder cargo publish commands by dependency#21552
Open
alamb wants to merge 2 commits intoapache:mainfrom
Open
Reorder cargo publish commands by dependency#21552alamb wants to merge 2 commits intoapache:mainfrom
cargo publish commands by dependency#21552alamb wants to merge 2 commits intoapache:mainfrom
Conversation
github-actions
bot
added
the
development-process
alamb
changed the title
cargo publish commands by dependency
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
1 participant
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.
Which issue does this PR close?
Rationale for this change
The publish command sequence in
dev/release/README.mdwas not ordered by crate dependencies. That means that I had to previously copy/paste these commands a few times to get them to work.What changes are included in this PR?
This PR reorders the documented
cargo publishcommands indev/release/README.mdso the listed crates are published in dependency order.Are these changes tested?
I tested it manually with the 52.5.0 release
The ordering was derived from the current workspace crate dependency graph by codex.
Are there any user-facing changes?
Yes. The release documentation now reflects a dependency-safe publish order for the DataFusion crates.