Support semver and gitflow

When using feature branches in gitflow the semver would be like 1.0.0-branchname.1+1. When releasing based on pre-releasetag the latest should be picked but when you get to to 10th commit the name would be it would pick (I have not found a way in gitversion to prefix the commit number with a .).
How can this be achieved?

Hi @rudibelt,

Thanks for getting in touch, and good question! Referring to the SemVer 2.0.0 spec, build metadata is ignored when determining version precedence. Meaning these two versions mentioned, differing only in the build metadata, are considered to have the same precedence, and Octopus will simply pick the first it finds that match this latest version.

I hope that helps! Let me know if you have any questions or concerns going forward. :slight_smile:

Best regards,