Closed felixonmars closed 4 years ago
From what I can determine, release “0.12.1” branched from commit 582fbd04. I don't see any commit in this repository which correctly represents the code released as “0.12.1”.
Some changes exist in ‘master’ after that commit, and do not include the changes made for release “0.12.1”.
So, I don't know where to add a new commit that makes the changes for that release. It's not commit 582fbd04 (because that does not match the actual code as released to PyPI). It's not any of the subsequent commits on ‘master’.
There should be a new commit made which exactly represents the source code as released for “0.12.1”, and that's where the “0.12.1” tag (and GitHub release) should be made. But that implies re-writing public history, so it's not ideal.
0.12.2 is also not tagged.
I've created the missing tags in GitHub.
It would be nice to keep PyPI releases and git tags in sync :)