"git-semver-tags" does not recognize all tags
See original GitHub issueWhen i run the command git tag --sort=-"v:refname"
in my project I can list all my tags corretly:
2.4.0
2.3.0
2.2.0
2.1.0
2.0.1
2.0.0
1.0.0
0.1.0-beta.9.1
0.1.0-beta.9
0.1.0-beta.7
0.1.0-beta.6
0.1.0-beta.5
0.1.0-beta.4
0.1.0-beta.3
0.1.0-beta.2
0.1.0-beta.1
0.1.0-beta
But running npx git-semver-tags
the result is:
2.0.0
1.0.0
0.1.0-beta.9.1
0.1.0-beta.9
0.1.0-beta.7
0.1.0-beta.6
0.1.0-beta.5
0.1.0-beta.4
0.1.0-beta.3
0.1.0-beta.2
0.1.0-beta.1
0.1.0-beta
This error produce that my CHANGELOG is not filled correctly because the latest tag is not recognized.
All my tags have been created in the same way
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:5
Top Results From Across the Web
How to make git describe use semver compatible tags only
1 tag. The main difficulty here, seems to be that the way to limit the tags by their name is based on globs,...
Read more >Managing Releases with Semantic Versioning and Git Tags
Michael Miles from MIT Sloan shares how to manage software releases with semantic versioning and Git tags. Learn about build numbers and how...
Read more >git-tag Documentation - Git
If no number is given to -n , only the first line is printed. If the tag is not annotated, the commit message...
Read more >Protected tags - GitLab Docs
If you select a protected tag's name, GitLab displays a list of all matching tags: ... Identify the branch names you do not...
Read more >Semantic versioning with Git tags - Travis Horn
Why should we put thought into version numbering? What's the best system for versioning? How can we implement it?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pablogm95
Run this command. This is what git-semver-tags sees as tags
To fix this, you need to tag the commits again. In your case, please find your commit SHA for 2.4.0
https://devconnected.com/how-to-create-git-tags/#Create_Git_Tag_for_Commit
same here