Deploy Release step should prevent picking releases from a different lifecycle
When creating a deployment 'parent' that utilizes the "Deploy A Release" step 'child', it's possible to create a 'parent' release with a 'child' release version that uses a different lifecycle. When attempting to deploy, the following cryptic error is returned:
The step failed: Activity <Child Step Name> on the Octopus Server failed with error 'The release has unresolved defects and cannot be deployed to this environment.
Once you have corrected these problems you can try again.
If the problem is related to a variable you will need to update the variables for this release or recreate the release for the changes to take effect.
If the problem is related to the deployment process you will need to create a new release for the changes to take effect.'.
When selecting a 'child' release version, only releases applicable to the same lifecycle should be displayed. The Latest column should display the latest release in the current lifecycle, and the Select Version popup should be filtered as well. Additionally, octo.exe deploy-release should pick the latest 'child' release in the current lifecycle.