Skip to content

Feature request: Make npm configuration optional #318

@iiian

Description

@iiian

Is it a core use case or an opt-in use case that semantic-release be able to publish to npm?

If not, I think it would increase the value of the setup tool to be able to produce configurations where npm publishing is only optional

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions