Skip to content

Fix signing key lookup for Maven publications - #4

Merged
riccardobl merged 1 commit into
jMonkeyEngine:masterfrom
toaster0123:fix/maven-publication-signing
Oct 31, 2026
Merged

riccardobl merged 1 commit into
jMonkeyEngine:masterfrom
toaster0123:fix/maven-publication-signing

Conversation

@toaster0123

Copy link
Copy Markdown
Contributor

The 2026-10-31 release run uploaded its artifacts but failed to close the Sonatype staging repository because all five signatures were missing. signMavenPublication was skipped even though the signing credentials were available.

Qualify the signing predicate with project.hasProperty('signingKey') so it checks the Gradle project property supplied through ORG_GRADLE_PROJECT_signingKey. This enables signing when the key is provided and preserves the existing skip behavior when it is absent.

Validation

An isolated reproduction using the module's build script, Gradle 9.8.0 and a temporary PGP key produced:

  • Original predicate: signing skipped, zero signature files.
  • Corrected predicate: five signature files generated and independently verified with GnuPG.

The patch changes only this predicate. No real credentials or Sonatype uploads were used for the local verification.

After merging, start a new release workflow dispatch from the corrected master. Rerunning the failed workflow would retain its original commit and the old signing predicate.

Check the project signingKey property in the signing predicate so CI does
not skip signature generation when the key is supplied through Gradle's
project-property environment variables.
@riccardobl
riccardobl merged commit e839d68 into jMonkeyEngine:master Oct 31, 2026
1 check passed
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.

2 participants