Skip to content

Fix signing key format and bump to v0.2.1#431

Merged
wow-miley merged 2 commits into
mainfrom
wow-miley/bump-v0.2.1
Feb 28, 2026
Merged

Fix signing key format and bump to v0.2.1#431
wow-miley merged 2 commits into
mainfrom
wow-miley/bump-v0.2.1

Conversation

@wow-miley
Copy link
Copy Markdown
Contributor

Summary

The SIGNING_KEY secret is base64-encoded (per original docs: gpg --armor --export-secret-keys KEY_ID | base64), but the vanniktech plugin's in-memory signing expects the raw ASCII-armored key. This adds a decode step before publishing.

Also bumps version to 0.2.1 since the v0.2.0 tag pointed to a commit before the publish workflow fix (#429).

Changes

  • Decode SIGNING_KEY from base64 before passing to Gradle as signingInMemoryKey
  • Bump ampereVersion to 0.2.1

🤖 Generated with Claude Code

wow-miley and others added 2 commits February 27, 2026 18:55
The v0.2.0 tag pointed to a commit before the publish workflow fix,
so re-releasing as 0.2.1 with the corrected task configuration.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The SIGNING_KEY secret is base64-encoded but the vanniktech plugin's
in-memory signing expects a raw ASCII-armored PGP key. Decode it in
a separate step before publishing.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@wow-miley wow-miley merged commit 13be4d7 into main Feb 28, 2026
2 checks passed
@wow-miley wow-miley deleted the wow-miley/bump-v0.2.1 branch February 28, 2026 01:18
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