consideRatio
commented
1 year ago These are the version bumping commits
- All the commits for 2.x are part of #13
- 2.0 bd22157
- 2.1 8abb333
- 2.2 61d6aab, was the bump commit, 441933d was the merge commit arriving directly after.
- The 3.0 commit was part of #14
- 3.0 c787d0b was the bump commit, cda47f3 was the merge commit arriving directly after.
- The 4.0 commit was in a dedicated bump PR: #20
- 4.0 03149b1 was the bump commit, ba42a02 was the merge commit arriving directly after.
Practically, I think the following tags should be made, where 2.2, 3.0, and 4.0 are the merge commits of the PRs where the version bumping commit were made.
git tag -am 2.0 2.0 bd22157
git tag -am 2.1 2.1 8abb333
git tag -am 2.2 2.2 441933d
git tag -am 3.0 3.0 cda47f3
git tag -am 4.0 4.0 ba42a02
I'd like to create a changelog retroactively using github-activity, but that relies on release being git tagged.
Is it okay if I retroactively create git tags, or maybe @yuvipanda has git tags already made but not pushed that can be pushed retroactively? It would help the use of
github-activityto generate the changelog. I see that the setup.py file has been updated reliably with new versions for each release on PyPI even though git tags hasn't been created/pushed reliably.Current PyPI releases
Click to expand
Current git history
Click to expand
``` * 25a0a5d - (HEAD -> main, origin/main, origin/HEAD, fork/main) Merge pull request #30 from yuvipanda/pre-commit-ci-update-config (2 weeks ago)