Skip to content

Add an option to avoid major bump when peerDeep has changed #822

@StarpTech

Description

@StarpTech

Problem

We have a monorepo https://github.com/wundergraph/wundergraph. We developed a package for our SDK @wundergraph/nextjs. The package has the SDK as peerDependency. After patching the SDK, the package is major bumped. We don't want this. This change was not communicated through a changeset. I think this defeats the purpose of a changeset.

Docs: https://github.com/changesets/changesets/blob/c68536edf4c04e7fdf5594ec9c69471cd86fd0ce/docs/decisions.md#the-versioning-of-peer-dependencies

Proposed solution

Provide an option to disable this behavior and make this part of the changeset.

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