release deploy returned error when using latest as input param for version

[bureku]

The bug

The command works if we explicitly specify the version, e.g. --version 1.0.0 but failed when using --version latest

Command to reproduce

octopus release deploy --space Default --project SOME_NAME --version latest --environment SOME.ENV --output-format basic --no-prompt

Outcome

 Octopus API error: Object reference not set to an instance of an object. []

Versions

cli: 1.7.1

Octopus Server: 2022.3.10594

Links

[benPearce1]

This is intentional behaviour.

The reason behind changing it was the definition of "latest" is not clear, could mean latest by time or latest by semver definition.

If you are using this in a CI context you would probably know which version you are wanting.

The output you are seeing is actually a bug though.

[DamienDaco]

This 'latest' feature used to exist in the previous octo cli, according to the doc.

We need it to simplify our deployments, as we would like to deploy the latest release available.