Skip to content

Fixed packages are only bumped up major version regardless of changeset specified version type #963

Closed

Description

@walt1992

Problem

I hava two packages [email protected] and [email protected] that a is depend on b.

and my config.json looks like below

{
  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
  "commit": false,
  "fixed": [["a", "b"]],
  "access": "restricted",
  "baseBranch": "main",
  "updateInternalDependencies": "patch",
}

In this condition, If I made a change on package a and made changeset to bumb up minor version.
After that, I ran changeset version to bump up packages version.
I expected the pacakge's versions were bumped up as v1.1.0 each. But they were turned into v2.0.0.

What is problem?

Activity

  1. changed the title [-]Fixed packages are onlu bumped up major version regradless of changeset specified version type[/-] [+]Fixed packages are only bumped up major version regradless of changeset specified version type[/+] on Sep 28, 2022
  2. changed the title [-]Fixed packages are only bumped up major version regradless of changeset specified version type[/-] [+]Fixed packages are only bumped up major version regardless of changeset specified version type[/+] on Sep 28, 2022
  3. Andarist commented on Sep 28, 2022

    @Andarist
    Member

    Please share a runnable repro case. It's hard to tell what is wrong in your case. Perhaps some of your packages are used as peer dependencies?

  4. walt1992 commented on Oct 13, 2022

    @walt1992
    Author

    Oh, I didn't aware the peerDependency is only bumped up major version.
    Thanks.

  5. Andarist commented on Oct 13, 2022

    @Andarist
    Member

    You can change the behavior around this using this flag in the config:

      "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
        "onlyUpdatePeerDependentsWhenOutOfRange": true
      }
  6. unional commented on Oct 26, 2022

    @unional

    You can change the behavior around this using this flag in the config:

    Note that seems like it is not working in 2.25.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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