IJHack / QtPass / 38207346999

93%

push

github

Init: changed recipients always reach the entries, or the user is told (#2017)

Init wrote the new .gpg-id and committed it before re-encrypting (#1685,
#1682); when that commit failed (a stale index.lock, a failing hook, no
Git identity) it stopped there. The list named the new recipients while
every entry stayed encrypted to the old ones: a person removed from the
list could still read everything, and only git's error said anything.

Now a failed .gpg-id commit still re-encrypts the entries to the new
recipients, without any Git step (no pull, no backup commit, no per-entry
commits, no push: each would fail the same way or publish a half-done
state), and ends with one message: the recipients were changed and the
entries re-encrypted, but nothing is committed or pushed yet; fix Git and
commit, or save the recipients again. If re-encryption fails too, the
message says the entries are still encrypted to the previous recipients.
The old list is not put back: with signing on, the generation record has
moved on and would refuse it as a rollback. With a working commit the
order is unchanged.

Init also refuses, writing nothing, while another re-encryption runs: the
new list would otherwise stand over entries left on the old recipients
with only a status-bar note.


Claude-Session: https://claude.ai/code/session_01VJygpMUf461yZgfAqwMJ6d

Signed-off-by: Anne Jan Brouwer <brouwer@annejan.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

33 of 36 new or added lines in 2 files covered. (91.67%)

9170 of 9875 relevant lines covered (92.86%)

193.86 hits per line