Closed IanButterworth closed 1 year ago
I'm realizing that git@github.com: Permission denied (publickey)
may actually just be a bad ssh key. I'll close this if confirmed
Indeed it was an old ssh key. Evidently this isn't needed as the referenced tag worked.
I've got a theory that the
git@github.com: Permission denied (publickey).
is a red herring and what's actually happening is unescaped chars in the tag message causing git to misunderstand the tag command TagBot is sending.As an example, below is the debug output from a failed TagBot run which has a huge and complicated message to pass into -m, and it failed.
So this PR changes to pass the tag message via a file via the the
tag -F
arg.I don't know how to test this. One option is if this passes we release it and see if it fixes it?
https://github.com/timholy/ProgressMeter.jl/actions/runs/5981657741/job/16230121798