I’m using the Deploy a release step in a complex deployment in a multi-channel environment. I’m opting to only deploy the release if it is a higher version than the current deployment to that environment.
Different channels have different version rules for the “child” release being deployed. I would expect in this situation that deployment condition would check the release that is current for that channel for the PARENT release in the environment - in fact, I am finding that the channel is being ignored, and the release being detected is the most recent deployed to ANY channel.
Just to add context - I’ve just been deploying the ‘overall’ release for a brand new channel - never deployed to before. The “deploy a release” step is skipped because some other channel already has a higher release version for the child!!!