[BUG] Changing version in prepublishOnly-Script has incorrect output

Current Behavior:

I have a prepublishOnly script like "npm version patch". However, npm tries to publish with previous version.

Expected Behavior:

Version of published package should be incremented (like it was for npm@6)

Steps To Reproduce:

Yeah, put a "prepublishOnly" script into package.json:

scripts: {
...
"prepublishOnly": "npm version patch",
...
}

Environment:

• npm: 7.5.5

Two notes:

• as mentioned above, with npm@6 this worked fine
• although the package would be published with the old version number, a git tag of the new one is commit'ed - which is a mess, of course

Edit: hmmm, when I tested with verdaccio, it seems the upload is right - it's only the output (version and tgz name) - nevertheless, that's still a mess ;-)

Reproduce the behavior with a package.json prepublishOnly script containing "npm version patch" under npm 7.5.5, then compare the displayed version and tgz name with npm@6. Check the result against the reported Verdaccio behavior: publishing appears to use the new version, while the output may still show the old one; done means the output is consistent with the published package and git tag.