From eb411ee92d30675a8d3d110f579692ea02949ccd Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Fri, 4 Sep 2020 10:00:48 +0800 Subject: Adjust signature key - please read if you verify installs/packages After a recent 'cleanup' operation that attempted to simplify my GPG key workflow with Yubikeys, it looks like my GPG installation has 'forgotten' how to interact with the key I typically used to sign GitPython releases. Since I never managed to establish a chain of trust with my only remaining 'good' key, for you this means you cannot trust new GitPython releases anymore. There is nothing I can do about except to apologize for the hassle. If you want to make constructive suggestions on how to fix this, I am happy to work with you on that. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Makefile') diff --git a/Makefile b/Makefile index e964d9ac..709813ff 100644 --- a/Makefile +++ b/Makefile @@ -17,7 +17,7 @@ release: clean force_release: clean git push --tags origin master python3 setup.py sdist bdist_wheel - twine upload -s -i 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60 dist/* + twine upload -s -i 27C50E7F590947D7273A741E85194C08421980C9 dist/* docker-build: docker build --quiet -t gitpython:xenial -f Dockerfile . -- cgit v1.2.3