Latest release/tag button refers to older, incorrect tag
See original GitHub issuePer title. Screenshot:
Repository: https://github.com/marzer/tomlplusplus
It was updating the button correctly with each release up until v0.3.0
, at which point it seems to have decided that’s the favorite and no further releases are important O_o
Perhaps also of note is the “new commits” indicator; it’s stuck at +3
even though it should actually say something closer to +11
, with respect to the tag it’s stuck on.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Swap "Latest release" on github - Stack Overflow
In the past I have solved this problem on my own personal projects by deleting the problematic older tag: git tag -d v0.1.0...
Read more >Auto-generator doesn't choose most current release as base diff
Our auto-generate release notes always refers back to the last release of the old format. Is there any way to change this other...
Read more >Git Tag Operations - Git Delete Tag & Git Update Tag - Tools QA
How to Delete tags & Update tags in Git? Different operations on Git Tags including Git Delete Tag and Git Update Tag with...
Read more >Can't create a release based on a Git tag that includes special ...
Navigate to a project's Tags page. · Click "New tag" · Enter !/"#%&'{}+,-.<>;=@]_`{|} as the Tag's name · Add a tag...
Read more ><img>: The Image Embed element - HTML - MDN Web Docs
Note: This attribute is mentioned in the latest W3C version, HTML 5.2, ... To do so, nest the <img> tag inside the <a>...
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
Maybe related to, or even fixed by, #2868? (not sure this made it into the latest release)
100% correct. Not yet released. So consider this fixed