Skip to content

Change the package.publish default to false on an edition boundary #12690

@epage

Description

@epage

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-edition-nextArea: may require a breaking change over an editionA-manifestArea: Cargo.toml issuesC-feature-requestCategory: 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.

    Type

    No type

    Projects

    Status

    Implemented

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions