Skip to content

Fix: add signing env vars to library build step - #17

Merged
Besi97 merged 1 commit into
mainfrom
fix/add-signing-to-build-steps
Aug 3, 2026
Merged

Besi97 merged 1 commit into
mainfrom
fix/add-signing-to-build-steps

Conversation

@Besi97

@Besi97 Besi97 commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Why

The library build step runs ./gradlew build publishToMavenLocal after the version has been changed from SNAPSHOT to a release version (e.g., 6.0.0-rc1). This triggers GPG signing because signAllPublications() is configured in build.gradle and the version no longer ends with -SNAPSHOT.

Without the signing environment variables, the build fails with:

> Task :signMavenPublication FAILED
> Cannot perform signing task ':signMavenPublication' because it has no configured signatory

Changes

  • Added signing environment variables to the "Build library" step:
    • ORG_GRADLE_PROJECT_signingInMemoryKey
    • ORG_GRADLE_PROJECT_signingInMemoryKeyPassword

Testing

Verified that:

  • ✅ Library build with SNAPSHOT version → signing skipped (works without env vars)
  • ❌ Library build with release version → signing required (fails without env vars)
  • ✅ Library build with release version + signing env vars → works
  • ✅ Gradle plugin build → no signing configured (works without env vars)
  • ✅ Example builds → no signing configured (works without env vars)

Note: Removed ORG_GRADLE_PROJECT_signingInMemoryKeyId because the plugin requires it in short 8-character format, and it's optional (auto-detected from the key).

The library build step runs 'publishToMavenLocal' with a non-SNAPSHOT version,
which triggers GPG signing. Without the signing env vars, this fails with
'no configured signatory' error.

The gradle plugin and example builds don't need signing because they don't
have signAllPublications() configured.
@Besi97
Besi97 merged commit dd53161 into main Aug 3, 2026
3 checks passed
@Besi97
Besi97 deleted the fix/add-signing-to-build-steps branch August 3, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant