Skip to content

Fix Maven Central publishing: decode base64-encoded signing key#4

Merged
wow-miley merged 1 commit intomainfrom
wow-miley/fix-maven-publishing
Feb 28, 2026
Merged

Fix Maven Central publishing: decode base64-encoded signing key#4
wow-miley merged 1 commit intomainfrom
wow-miley/fix-maven-publishing

Conversation

@wow-miley
Copy link
Contributor

Summary

The vanniktech maven-publish plugin expects raw ASCII-armored PGP key material, but the SIGNING_KEY GitHub secret is base64-encoded. This causes signing to fail during publish workflows.

Add a decode step that converts the base64-encoded secret to plain text before passing it to the plugin via the ORG_GRADLE_PROJECT_signingInMemoryKey environment variable.

Changes

  • Added "Decode signing key" workflow step that base64-decodes the signing key secret
  • Updated the "Publish to Maven Central" step to use the decoded key from /tmp/signing-key.asc
  • Removed the direct reference to the base64-encoded SIGNING_KEY secret from the environment

🤖 Generated with Claude Code

The vanniktech maven-publish plugin expects raw ASCII-armored PGP key material, but the SIGNING_KEY secret is base64-encoded. Add a decode step to convert the secret to plain text before passing it to the plugin via ORG_GRADLE_PROJECT_signingInMemoryKey environment variable.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@wow-miley wow-miley merged commit fd62e33 into main Feb 28, 2026
1 check passed
@wow-miley wow-miley deleted the wow-miley/fix-maven-publishing branch March 5, 2026 03:02
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