Hi, we have some projects that use opinionated frameworks that just love to bake in environment configurations as part of their build process. It blows IMHO, but it is also ubiquitous with some frameworks cough Angular cough
As a result we have some packages where the SemVer differs only by the build information, based the environment it was built for, e.g.
1.2.3+abcd123.useast. We would like to use Channel Version Rules to ensure the correct configuration uses the correct Channel only. And to enable the use of Automatic Release Creation.
Our reading of the documentation suggests we can apply a regex match to the SemVer pre-release information but not on the SemVer build information? It that right? If so, we would like to request a second regex is added to the dialog for version rules for matching on build metadata. In that way you have full SemVer coverage.
I realize we could probably fake our way though this by placing the build information in the ‘pre-release version’ slot of SemVer, but that wouldn’t make SemVer sense since these packages are not in any sense ‘pre-releases’.