Reflect the addition of the -p flag in Cargo 1.56 in chapter 14 #3051
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
In Cargo 1.56 (2021-10-21), support for publishing a package from a Cargo workspace was added to the `cargo publish` command. The book however still mentioned that it wasn't possible to publish a package unless you navigated into the respective package directory and published from there. This commit fixes the text which mentioned it isn't possible, and the text was instead changed to be an example of how the flag can be used (similar to the `cargo test -p [spec]` above it). The manual-regeneration comment was taken from Chapter 14.2 (Publishing a Crate to Crates.io) as the example was similar to the publish a crate example there.
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.
In Cargo 1.56 (2021-10-21) [1][2], support for publishing a package from a Cargo workspace was added to the
cargo publishcommand.The book however still mentioned that it wasn't possible to publish a package unless you were navigated into the respective package and published from there.
This commit fixes the text which mentioned it isn't possible, and the text
was instead changed to be an example of how the flag can be used (similar to
the
cargo test -p [spec]above it).The manual-regeneration comment was taken from Chapter 14.2 (Publishing a Crate
to Crates.io) as the example was similar to the publish a crate example there.
[1] rust-lang/cargo#9559
[2] /~https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#added-4