-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed
Labels
A-edition-nextArea: may require a breaking change over an editionArea: may require a breaking change over an editionA-manifestArea: Cargo.toml issuesArea: Cargo.toml issuesC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-team-inputStatus: Needs input from team on whether/how to proceed.Status: Needs input from team on whether/how to proceed.
Description
Problem
For Cargo.toml
, package.publish
defaults to true
.
For "cargo script", package.publish
defaults to false
.
I also feel like publishing should be more of an explicit choice. especially when working on a workspace where a cargo release
(and eventually cargo publish
in #1169) can release everything in the workspace.
Proposed Solution
By changing the default, we close the documentation gap between these features.
Notes
See also #6153
Muscraft, edmorley, Goffen and greyblake
Metadata
Metadata
Assignees
Labels
A-edition-nextArea: may require a breaking change over an editionArea: may require a breaking change over an editionA-manifestArea: Cargo.toml issuesArea: Cargo.toml issuesC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-team-inputStatus: Needs input from team on whether/how to proceed.Status: Needs input from team on whether/how to proceed.
Type
Projects
Status
Implemented