Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Wrong version on Mainline with tag

See original GitHub issue

Describe the bug I Was testing GitVersion for the Mainline Mode. I tagged my latest commit to 0.1.0 After tagging i used command gitversion /config on my main branch. The next calculated version i get was 0.1.4(based upon my prev commits)

Expected Behavior

Expected behavior is that next calculated version should have been 0.1.0 as i have explicityly tagged Another interesting behavior was when i tagged as 0.1.1 then next calculated version was 0.1.1

Actual Behavior

Calculate Version becomes 0.1.4

Possible Fix

Steps to Reproduce

Context

Your Environment

Version Used:
Operating System and version (Windows 10, Ubuntu 18.04):
Link to your project:
Link to your CI build (if appropriate):

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

DmytroSokhachcommented, Mar 17, 2021

@asbjornu thank you for fast reply! Indeed was using Mainline and next-version, after updating to 5+ didn’t notice the moment when it stopped working. Adding tag to particular commit in master did it’s job.

1reaction

asbjornucommented, Mar 17, 2021

I don’t think this bug is related to next-version, @DmytroSokhach as @Gaurav-Puri101187 is using git tag. Sounds like you’re experiencing #2441 instead, which is remedied by removing next-version and adding a git tag instead.

Top Results From Across the Web

Why does checking out a git tag bring the wrong version of ...

1 Answer 1 ... The problem is the -b option. ... This means that you're creating a new branch called tagname . Since...

Configuration

If you are using next-version and are experiencing weird versioning behaviour, please remove it, create a git tag with an appropriate version number...

How to use GitVersion to get sensible versioning

As you can see the hotfix version is 1.2.* but in your example it is 1.1.1-beta.1+1. Should I still merge and tag the...

Patterns for Managing Source Code Branches - Martin Fowler

I define a codeline as a particular sequence of versions of the code base. It can end in a tag, be a branch,...

Religion and Intimate Partner Violence: Understanding the ...

For conservative Protestant pastors who are quite willing to label violence as sinful and wrong behavior but reticent about working with those outside...