You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,6 +154,10 @@ The `Release` workflow will:
154
154
155
155
Troubleshooting
156
156
- If you see `base64: invalid input` or `gpg: no valid OpenPGP data found`, paste the ASCII‑armored private key directly into the `GPG_PRIVATE_KEY` secret (not base64). The workflow auto‑detects and imports either format.
157
+
- If Central reports invalid signature or cannot find your public key by fingerprint:
158
+
- Upload your public key to a supported keyserver, e.g. `keys.openpgp.org`, and verify the email identity used for the key (you will receive a verification email).
159
+
- Alternatively, add the same public key in the Sonatype Central portal under your account’s PGP keys.
160
+
- Make sure the key fingerprint in CI matches the one you uploaded (the workflow prints it during release).
0 commit comments