We are currently running version 18.104.22.168 and are experiencing an issue with deletion of releases. One of our more common scenarios is to pre-stage a release for promotion. In this scenario the current duplicate logic checks for release name make this difficult without changes to our release numbering convention. Currently we create a release for a project without deploying it. When it is determined that this release needs to either be recreated from a newer build (prior to sending to the deployment teams) we delete the release in Octopus with the expectation that since it hadn’t ever been deployed we could create a new release with the same numbering. Prior to our upgrade to 22.214.171.124 we could perform this operation any number of times until the release was deployed to at minimum 1 environment. Now we are lengthening our release numbers artificially before sending deployments to the deployment team which causes some confusion in referencing releases. We commonly release multiple projects under the same release number as they are aligned for production delivery on production target date.
Is there a way to remove this duplicate check or to clean up all history of the undeployed release number so that it can be re-used?