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
Adjust CI and Gradle signing to avoid multiline secret issues and switch to new publish tasks.
- .github/workflows/deploy.yml: remove GPG import, expose SIGNING_KEY/PASSWORD and MAVEN creds via env, write credentials to ~/.gradle/gradle.properties, write the multiline signing key to /tmp/signing-key.txt and reference it, and change Gradle invocations from :*:publish to :*:publishToCentralPortal for release and snapshot flows.
- moss*/build.gradle: change signing logic to treat the signingKey property as a file path, read its contents, and call useInMemoryPgpKeys only when key content is available before signing publications.
This prevents problems with multiline secrets in GitHub Actions and ensures Gradle receives an in-memory PGP key correctly while using the updated publishing tasks.
0 commit comments