pnpm up changes package.json ignoring semver

[pitgrap]

Hi, I have a question about "pnpm up":

We're migrating our workspace from yarn to pnpm. Everything works fine so far.
But I found one difference I don't like.

When I ran "yarn upgrade", every dependency was updated according to the semantic version. This was done only in the lock file and the package.json kept the same (because of semver). Afterr migrating I did the same with "pnpm update", but now also every package.json has been changed, which is not necessary (because of semver). Of course, I could manually revert the changes to the package.json, run "pnpm install" and get the same result. But that feels... wrong.

So, do I miss something? Would it be a feature request to add a flag to not update the package.json? Or is this a bug?