The new "Deploy a Release" step is great! However, it was unclear to me at the time of setting up the steps that the "Deploy a Release" step does not actually support creation of a release before deployment--the release must already be created in the child projects before deploying.

While this step is definitely headed in the right direction, in my opinion, I would think this feature would be even more useful if it also supported the ability to create a release in the child project(s) before deploying.

The package versions are already supplied to the projects when creating the parent project's release, so I would think it could naturally use the package version supplied at the time of parent release creation to create releases in the child projects when deploying. I'm not really sure what to suggest if that release already exists in a child project, though--maybe just prevent the release until the conflict is resolved.

Thanks!