OctopusDeploy
Channel version range not being inclusive of base versions with pre-release tag
Severity
1 customer reported, recreated on latest cloud
Version
2025.4.1729, 2025.4.1893
Latest Version
None
What happened?
Trying to design a channel versioning rule that tries to be inclusive to a base build number does not include the base x.y.0 build in what can be retreived when a pre-release tag is used
Reproduction
- Go to any channel and start designing a versioing rule
- Add in a version number being inclusive with a major and minor version (i.e.
[7.1,)) - Add in the regex for any pre-release tag (
^[^\+].*) - Add in the following versions to the sample versions:
- 7.1-dev
- 7.1.0-dev
- 7.1.1-dev
Out of all the above versions, only 7.1.1-dev is said to be valid, when the others should be as well.
If you then remove the pre-release regex, and the tags off the sample versions, they will allow show as valid in the samples.
Error and Stacktrace
More Information
With pre-release tags
Without pre-release tags
Workaround
Current workaround is to remove any minor, build, etc versioning numbers that you may have on the version range. This should allow your versions to work with pre-release tags.
i.e. instead of [7.1,) you would have [7,)
Setting to base zero versions will also work
i.e. [7.0.0.0,) will allow 7.1.0.1-alpha
