This would be a great addition for us as well. Like others here we also base our version numbering on the nuget package version and channel (1.2.3-dev, 1.2.3-qa, 1.2.3-prod...)
Understanding that there are complications with this feature (multiple packages per deployments and so on) my suggestion to solve this would be to add a "suffix" option when defining version number from an included package.
So at "Settings" -> "Release Versioning" -> "Use the version number from an included package" maybe it's possible to add an optional input field for suffix. This way we'd be able to automatically create version numbering based on a concrete package step in the process + a custom suffix (ie. channel name).
Alexander Rauan
supported this idea
·
This would be a great addition for us as well. Like others here we also base our version numbering on the nuget package version and channel (1.2.3-dev, 1.2.3-qa, 1.2.3-prod...)
Understanding that there are complications with this feature (multiple packages per deployments and so on) my suggestion to solve this would be to add a "suffix" option when defining version number from an included package.
So at "Settings" -> "Release Versioning" -> "Use the version number from an included package" maybe it's possible to add an optional input field for suffix. This way we'd be able to automatically create version numbering based on a concrete package step in the process + a custom suffix (ie. channel name).