Unexpected peerdependent bump to 1.0.0 in pre mode

Problem

I have a branch in pre mode, and I don’t understand why Changesets is planning on bumping this peerdependent to 1.0.0, even if the dependency’s new version perfectly satisfies the specified range (0.11 is >= 0.9, right?)

I would have expected the specified peer dependency range to remain intact, and the dependent’s version not to be bumped to 1.0.0.

To clarify, bumping the peer dependency range would be acceptable (even if I did not expect it), but the bump to 1.0.0 is not.

My config.json:

{
  "$schema": "https://unpkg.com/@changesets/config@2.0.0/schema.json",
  "changelog": "@changesets/cli/changelog",
  "commit": false,
  "fixed": [],
  "linked": [],
  "access": "public",
  "baseBranch": "main",
  "updateInternalDependencies": "minor",
  "ignore": [],
  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
    "onlyUpdatePeerDependentsWhenOutOfRange": true
  }
}

Version of changesets in use is 2.24.4.

Link to PR and repository: https://github.com/hmans/miniplex/pull/126/files

Thanks!

[alvarosabu]

I’m having the same issue, pkgB has pkgA as peerDependency.

PkgB is bumped to 1.0.0 instead of next minor version.

PkgA is bumped to next minor correctly.

[Andarist]

One additional idea is that perhaps for the >= range we could “upgrade” it to smth like “>=0.9.0 || >=0.11.0-0.next.0”:

require('semver').satisfies('0.11.0-next.0', '>=0.9.0 || >=0.11.0-next.0') // true

Then we could even “bring back” the original range when exiting the premode.