Error Message
Invalid Version Arg.
Symptom
The parameter is invalid.
Possible Causes
An invalid semantic version is configured for the ohpm version <newversion> command, for example, ohpm version a.b.c.
Solution
Set newversion to a valid semantic version.
Error Message
Invalid Origin Version.
Symptom
The version number is invalid.
Possible Causes
The version field in the module-level oh-package.json5 file is set to an invalid semantic version, for example, "version": "a.b.c".
Solution
Set the version field to a valid semantic version in the module-level oh-package.json5 file.
Error Message
Not Exist.
Symptom
The version field does not exist.
Possible Causes
The version number is not configured for the dependency package.
Solution
Add the version field to oh-package.json5 and set it to a valid value.
Error Message
No Change.
Symptom
The version number is not changed.
Possible Causes
The version field in the module-level oh-package.json5 file is not changed. For example, the current version is 1.0.0, but the ohpm version 1.0.0 command is executed.
Solution
Check the value of version in the module-level oh-package.json5 file and ensure that it is different from the current version number.