Issue creating a release from Octo.exe while project is set to use version of a package

[Dalmirog-zz]

Octo.exe version: 3.3.16
Octopus Server: 3.3.15

• Project is set with release versioning "Use the version number from an included package"
• Run Octo.exe create-release with parameters server,apikey,Project,PackageVersion

If --pacakgeversion=MyDeployStep:2.0.0, the expected outcome would be for Octopus to try to create a release with version 2.0.0. What happens instead is that Octopus tries to create a release using the whole string MyDeployStep:2.0.0 as version number.

Body of the POST call

[slewis74]

Will the package parameter cover what you are after in the above scenario? The packageversion is to specify the package version without a StepName.
I've updated the parameter parsing to validate that you can only give it a semantic version for packageversion. Have tested a variety of scenarios and all seem to be giving the correct behaviour.

[octoreleasebot]

Release Note: Octo.exe now ensures that packageversion, if specified, is a semantic version

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.