diff options
-rw-r--r-- | README.md | 2 | ||||
-rw-r--r-- | VERSION | 2 | ||||
-rw-r--r-- | doc/source/changes.rst | 11 |
3 files changed, 12 insertions, 3 deletions
@@ -117,7 +117,7 @@ Please have a look at the [contributions file][contributing]. * Update/verify the version in the `VERSION` file * Update/verify that the changelog has been updated * Commit everything -* Run `git tag <version>` to tag the version in Git +* Run `git tag -s <version>` to tag the version in Git * Run `make release` * Finally, set the upcoming version in the `VERSION` file, usually be incrementing the patch level, and possibly by appending `-dev`. Probably you @@ -1 +1 @@ -2.1.7 +2.1.8 diff --git a/doc/source/changes.rst b/doc/source/changes.rst index 4aedf936..70f66a7d 100644 --- a/doc/source/changes.rst +++ b/doc/source/changes.rst @@ -2,7 +2,16 @@ Changelog ========= -2.1.6 - Bugfixes +2.1.8 - bugfixes +==================================== + +See the following for (most) details: +https://github.com/gitpython-developers/GitPython/milestone/23?closed=1 + +or run have a look at the difference between tags v2.1.7 and v2.1.8: +https://github.com/gitpython-developers/GitPython/compare/2.1.7...2.1.8 + +2.1.6 - bugfixes ==================================== * support for worktrees |