Version tag is out of date
See original GitHub issueIn the 0.2.0
release I neglected to change the __version__
tag at the top of the file from 0.1.2
to 0.2.0
. Making a note of this here, for anyone that uses that tag when reporting an issue. If/when I release a 0.2.1
I will fix this, but it’s too minor an issue to increment the version history for!
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Tags in this repo are not up to date · Issue #783 - GitHub
The tags in this repo do not seem to correspond to the published version of the spec. For example, the published version of...
Read more >Change date of git tag (or GitHub Release based on it)
It seems that in new versions of git (tested on 2.33.0), when you git tag , the new tag's date will be set...
Read more >A Tutorial for Tagging Releases in Git - DEV Community
Tags are a simple aspect of Git, they allow you to identify specific release versions of your code. You can think of a...
Read more >Git - Tagging - Git SCM
Checking out Tags. If you want to view the versions of files a tag is pointing to, you can do a git checkout...
Read more >maintenance - using git, bringing old tagged releases up to date
Tag the head commit of that branch, and maintain as needed, deprecating maintenance for older versions. git rebase to rewrite history and bring ......
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
It’s useful for more than just that. You can’t really go back from tarball to git without the tag without a bit of sleuthing (e.g., the version wasn’t right this time, so you can’t necessarily rely on that). The PyPI tarball doesn’t contain tests, so if I want to run tests when making a package, I need to pull the tagged version from GitHub. Also, if any patches are needed downstream, the tag makes this simple to do.
I’ve created the tag now, thanks for the spot.