We are relying on the *Version Packages* auto PR to publish to NPM. But we recently found that minor and patch changes are triggering major upgrades, 1. The behaviour is correct up to this PR. https://github.com/gqty-dev/gqty/pull/1841 2. Incorrect major pump on `@gqty/logger`, `@gqty/react` and `@gqty/subscriptions` https://github.com/gqty-dev/gqty/pull/1845 3. This PR seems correct, albeit pumping on an incorrect major. https://github.com/gqty-dev/gqty/pull/1859 4. Again, incorrect major pump on `@gqty/logger`, `@gqty/react` and `@gqty/subscriptions` https://github.com/gqty-dev/gqty/pull/1903 Am I doing anything wrong with my changeset files?
Activity
Pewtro commentedon Aug 9, 2024
I also pretty frequently run into this issue, for example: Pewtro/blizzard-api#29
bluwy commentedon May 15, 2026
I'd suggest reporting this to https://github.com/changesets/changesets as version bumps are handled there. It's likely due to implicit peer dep update that requires a major bump.