Generally, this should not be a problem when bumpping up a single module without version, and it is meaningless to have a single module without version when using bumpp
However, for monorepos, since -r or recursive option will use current git version as current version, once some modules are marked as private without version specified in monorepo, current implementation will append the version property to the manifest (e.g. package.json) and produce unexpected outcomes.
This PR suggest to skip the modification if version is not set.
Description
version, and it is meaningless to have a single module withoutversionwhen usingbumpp-rorrecursiveoption will use current git version as current version, once some modules are marked as private withoutversionspecified in monorepo, current implementation will append theversionproperty to the manifest (e.g.package.json) and produce unexpected outcomes.Linked Issues
Additional context
Optional
versionif not publishing: https://docs.npmjs.com/cli/v10/configuring-npm/package-json#version