-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure running 'gpg --batch --passphrase #172
Comments
gpg (GnuPG) 1.4.23
gpg: directory `/home/runner/.gnupg' created
gpg: can't open `/usr/local/share/gnupg/options.skel': No such file or directory
gpg: keyring `/home/runner/.gnupg/secring.gpg' created
gpg: keyring `/home/runner/.gnupg/pubring.gpg' created
base64: invalid input
gpg: no valid OpenPGP data found.
gpg: key FFFFFFFF: no user ID
gpg: Total number processed: 1
gpg: secret keys read: 1 It says "base64: invalid input". Maybe sbt-ci-release should fail fast there? |
OK, it was my mistake. I generated the keys in a system that was GPG2 and GitHub Actions currently is 1.4.
|
Actually, nope, that didn't help. I'm at lost. I've retried this so many times. I don't know what I'm doing wrong |
OK, I figured it out! |
Closing since this appears resolved |
I'm getting the following error in GitHub actions.
Back when I had a travis flow this was working.
The snapshots are OK.
The text was updated successfully, but these errors were encountered: