Expired PGP keys: can we fail the release immediately, with clearer messaging? #49
Description
The current error message for an expired PGP key is quite hard to find, and happens at the Sign stage, when we could probably establish the key is bad earlier on, at the Init stage - and maybe provide a better message:
Creating release tag (including artifact hashes)
error: gpg failed to sign the data:
[GNUPG:] KEYEXPIRED 1732894550
[GNUPG:] KEY_CONSIDERED E3A34749D7B9948D0AA146D06950682D8454F077 3
gpg: skipped "E3A34749D7B9948D0AA146D06950682D8454F077": Unusable secret key
[GNUPG:] INV_SGNR 9 E3A34749D7B9948D0AA146D06950682D8454F077
[GNUPG:] FAILURE sign 54
gpg: signing failed: Unusable secret key
error: unable to sign the tag
The tag message has been left in .git/TAG_EDITMSG
Error: Process completed with exit code 128.
See also #48 .