From 81f312115ed768a4452adf842ba0cd4820e0cc74 Mon Sep 17 00:00:00 2001 From: Paul Date: Tue, 6 Aug 2024 13:55:55 -0400 Subject: [PATCH] Update git command to summarize changes since latest release --- docs/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release.md b/docs/release.md index 303fd19..e7fe40f 100644 --- a/docs/release.md +++ b/docs/release.md @@ -31,7 +31,7 @@ Single commit releases and patch releases don't need a release candidate. 1. Bump version in kmax/about.py (perhaps this should be automated from [or to] git somehow?) 2. Add a new tag for the version in git, prefixed with a "v", e.g., v4.3.1, annotated with a description of the new version. Use this to get a log of changes - git log --pretty="- %s" v4.5.2..HEAD + git log --no-merges --pretty="- %s" $(git describe --tag --abbrev=0)..HEAD 3. Make a release on github for major, minor, and patch version changes, using the same description from above for the release. 4. Publish to pypi (see scripts/pypi.sh)