Summary

When we have a fixed version group and add a single minor changeset for one package in that group, npx changeset status reports that every package in the fixed set needs a major bump. We expect only a minor bump for the entire fixed group.

Reproduction

1. Clone https://github.com/ydb-platform/ydb-js-sdk and check out commit 9455d9b.
2. Note .changeset/config.json contains a fixed group with these packages:
   [
   "@ydbjs/abortable",
   "@ydbjs/api",
   "@ydbjs/auth",
   "@ydbjs/core",
   "@ydbjs/debug",
   "@ydbjs/error",
   "@ydbjs/query",
   "@ydbjs/retry",
   "@ydbjs/topic",
   "@ydbjs/value"
   ]
3. There is a single changeset .changeset/heavy-facts-happen.md whose frontmatter is:

   ---
   '@ydbjs/topic': minor
   ---

4. Run npx changeset status.

Expected result

Because the highest bump type within the fixed group is minor, the status report should list the group under “Packages to be bumped at minor”, and the next release should be 6.1.0.

Actual result

npx changeset status prints all packages from the fixed group under “Packages to be bumped at major”:

🦋 info Packages to be bumped at patch:
🦋 info
🦋 - @ydbjs/auth-yandex-cloud
🦋 ---
🦋 info NO packages to be bumped at minor
🦋 ---
🦋 info Packages to be bumped at major:
🦋 info
🦋 - @ydbjs/topic
🦋 - @ydbjs/abortable
🦋 - @ydbjs/api
🦋 - @ydbjs/auth
🦋 - @ydbjs/core
🦋 - @ydbjs/debug
🦋 - @ydbjs/error
🦋 - @ydbjs/query
🦋 - @ydbjs/retry
🦋 - @ydbjs/value

Additional context

• npx changeset --version → 2.29.7
• Node.js v24.7.0, npm 11.6.2
• All packages in the fixed group are currently at version 6.0.5.