Commit 4c993ea
committed
Do not use gpg2 with sbt-ci-release
While trying to release 0.8.0, I hit an issue with gpg2:
```
Running ci-release.
branch=refs/tags/v0.8.0
gpg (GnuPG) 2.2.4
libgcrypt 1.8.1
...
gpg: key 96BDF10FFAB8B6A6/96BDF10FFAB8B6A6: error sending to agent: Inappropriate ioctl for device
gpg: error building skey array: Inappropriate ioctl for device
gpg: Total number processed: 1
gpg: imported: 1
gpg: secret keys read: 1
...
[error] gpg: no default secret key: No secret key
[error] gpg: signing failed: No secret key
[error] java.lang.RuntimeException: Failure running 'gpg --batch --passphrase *** --detach-sign --armor --use-agent --output /home/runner/work/scala-steward/scala-steward/modules/mill-plugin/.jvm/target/scala-2.12/scala-steward-mill-plugin_2.12-0.8.0.pom.asc /home/runner/work/scala-steward/scala-steward/modules/mill-plugin/.jvm/target/scala-2.12/scala-steward-mill-plugin_2.12-0.8.0.pom'. Exit code: 2
```
I'm now trying the workaround mentioned in https://github.com/djspiewak/sbt-github-actions#integration-with-sbt-ci-release.1 parent 6a1cdad commit 4c993ea
2 files changed
+4
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
174 | 174 | | |
175 | 175 | | |
176 | 176 | | |
| 177 | + | |
| 178 | + | |
177 | 179 | | |
178 | 180 | | |
179 | 181 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
| 24 | + | |
| 25 | + | |
24 | 26 | | |
25 | 27 | | |
26 | 28 | | |
| |||
0 commit comments