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.

Update tags on master repository

See original GitHub issue

Reoccurring issue: tags on master are not up-to-date

Last tag on master is set to v7.2.0-preview.1 that causes the local builds of up-to-date PowerShell repository to show wrong build number:

Steps to reproduce

git fetch --all --tags
git describe

Expected behavior

v7.2.0-preview.2

Actual behavior

v7.2.0-preview.1-144-g3f95fc491

Issue Analytics

State:
Created 3 years ago
Comments:6

Top GitHub Comments

2reactions

iSazonovcommented, Dec 16, 2020

@kborowinski Current workflow is - MSFT team creates a release branch internally, prepares new release, after the release they merge the release branch to master one. If after the merge you see any issues (tags, docs, links and so on) please report.

1reaction

rjmholtcommented, Dec 16, 2020

So I think git fetch --tags would solve the problem, but I’ve now merged the PR above so git fetch might also solve it now. I’m slightly concerned though since I omitted a bugfix commit that the release used (rather than add a reversion commit) and that might be an issue for this