Reason for non-consecutive version numbers #3118
|
I'm just curious: What's the reason behind version numbers not being consecutive? E.g., after 3.0.0 came 3.0.7, then 3.0.11. Looking at the Renovate dashboard, I was wondering how we were so much behind within a few days from 3.0.7 :). Thank you! |
Answered by
philon-msft
Jun 30, 2026
Replies: 1 comment · 1 reply
|
StackExchange.Redisuses Nerdbank.GitVersioning, so the build component of the version is incremented for each commit to main, rather than each release. Releases that contain multiple new commits will jump multiple build versions |
1 reply
|
Ah OK, thank you! |
Answer selected by
Piedone
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
StackExchange.Redisuses Nerdbank.GitVersioning, so the build component of the version is incremented for each commit to main, rather than each release. Releases that contain multiple new commits will jump multiple build versions