Oliver Ford

You have two keygrips there: https://github.com/goreleaser/goreleaser-action/runs/4262700166?check_suite_focus=true#step:4:39 suggests it's not just a signing key?

Oh sorry think I misunderstood your comment. Yes, agreed.

@crazy-max Any progress with this? I just tried changing the key to one with encryption too; (RSA4096) not just the signing key, and I get the same: https://github.com/OJFord/terraform-provider-wireguard/runs/4803454647

Perhaps 4096-bit RSA is what's common and somehow the problem? Is it worth trying EC, or lesser-bitted RSA?

> @OJFord Are you able to repro with `uses: crazy-max/ghaction-import-gpg@v3`?: > > ```yaml > - name: Import GPG key > id: import_gpg > uses: crazy-max/ghaction-import-gpg@v3 > with: > gpg-private-key: ${{...

This seems related to actions/runner#241? I don't understand why seemingly only I have this issue with goreleaser-action though!

With `pinentry-mode loopback` in my `~/.gnupg/gpg.conf` and `allow-loopback-pinentry` in `gpg-agent.conf` (and having subsequently reloaded `gpg-agent`), I get the same identified in #201: > release failed after 395.00s error=sign: gpg failed:...

Feel silly for not thinking of this sooner, but creating the key without a passphrase seems to work around it successfully.

I assume it's from git yes, trying to parse the output from `diff-so-fancy --patch`. The above diff with no `interactive.diffFilter`: ```diff diff --git a/empty b/empty index e69de29bb..2efad47f3 100644 --- a/empty...

May be a git _bug_ of course. Delta facing the same issue: dandavison/delta/issues/1114 Some recent changes (new in 2.37) https://github.com/git/git/commits/master/add-patch.c, > "git add -p" rewritten in C regressed hunk splitting...