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] 5.6.5 Not finding Tag in master repo

See original GitHub issue

My master branch has a Tag 6.1.0. It get correctly picked up by version 5.6.4

  INFO [01/28/21 13:53:18:60] Begin: Calculating base versions
    INFO [01/28/21 13:53:18:62] Fallback base version: 0.1.0 with commit count source 1f34f7b0477ebdaba3db9de21c9bc4aa1ba432d9
    INFO [01/28/21 13:53:18:67] Git tag '6.1.0': 6.1.0 with commit count source ee2c143847ae685ad96dedb7020bf563ac535bea
    INFO [01/28/21 13:53:18:72] Found multiple base versions which will produce the same SemVer (6.2.0), taking oldest source for commit counting (Git tag '6.1.0')
    INFO [01/28/21 13:53:18:72] Base version used: Git tag '6.1.0': 6.1.0 with commit count source ee2c143847ae685ad96dedb7020bf563ac535bea
  INFO [01/28/21 13:53:18:72] End: Calculating base versions (Took: 117.57ms)

but in version 5.6.5 it is not found:

INFO [02/09/21 7:24:04:69] Begin: Calculating base versions
    INFO [02/09/21 7:24:04:71] Fallback base version: 0.1.0 with commit count source 1f34f7b0477ebdaba3db9de21c9bc4aa1ba432d9
    INFO [02/09/21 7:24:04:80] Found multiple base versions which will produce the same SemVer (0.2.0), taking oldest source for commit counting (Fallback base version)
    INFO [02/09/21 7:24:04:80] Base version used: Fallback base version: 0.1.0 with commit count source 1f34f7b0477ebdaba3db9de21c9bc4aa1ba432d9
  INFO [02/09/21 7:24:04:80] End: Calculating base versions (Took: 118.04ms)

Issue Analytics

State:
Created 3 years ago
Comments:45 (23 by maintainers)

Top GitHub Comments

1reaction

asbjornucommented, Mar 1, 2022

Already published versions of the GitTools task should continue to work, @superjulius. If they are removed, that’s beyond our control and up to Microsoft, if anything. There is no plan to fix this beyond us accepting a pull request that fixes it. As none of the maintainers seem to have this issue, we have no incentive to work on it, unfortunately.

1reaction

superjuliuscommented, Mar 1, 2022

We are looking to replace the deprecated GitVersion with the latest GitTools task in Azure Pipelines but we also hit the versioning issue as our repo is using master naming

@asbjornu @arturcic Is it safe to explicitly target 5.6.4 (no risk of depreciation)? Is there any plan to fix this in 5.x? or more likely to be addressed in 6.x?

Top Results From Across the Web

Releases · GitTools/GitVersion

#2881 [Bug] GitVersion is extremely slow (25 minutes) ... #2590 [Bug] 5.6.5 Not finding Tag in master repo; #2605 [Bug] GitVersion is crashing...

git - Verify if a tag was done in the master branch

The issue here is that an annotated tag has an actual repository object, of type "annotated tag", to which the name points; using...

How to Get Started with GIT and work with GIT Remote Repo

Make some changes and staged. $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit ...

Latest git tag not recognized when installing requirements.txt

I have a dependency in my requirements.txt that comes from another git repo (not mine, but I have access to it). Yesterday I...

Release notes for Windows

This article contains information about recent changes to the Zoom app for Windows, including new and enhanced features, updates to existing features, and...