Skip to content

Harmonize signing workflows with the repo's actual secret names - #35

Merged
Marcogn merged 1 commit into
mainfrom
claude/harmonize-android-secret-names
Sep 6, 2026
Merged

Harmonize signing workflows with the repo's actual secret names#35
Marcogn merged 1 commit into
mainfrom
claude/harmonize-android-secret-names

Conversation

@Marcogn

@Marcogn Marcogn commented Sep 6, 2026

Copy link
Copy Markdown
Owner

What

The four Android signing secrets already exist in this repo under the ANDROID_ prefix (ANDROID_KEYSTORE_BASE64, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, ANDROID_KEY_PASSWORD), but build-apk.yml and release.yml still referenced them as secrets.RELEASE_* — a mismatch that would make both workflows read empty secrets and fail signing at build time.

Changes

  • .github/workflows/build-apk.yml, .github/workflows/release.yml: updated only the secrets.RELEASE_*secrets.ANDROID_* references (plus one stale comment naming the old secret in prose).
  • docs/release-signing.md: updated the secret-name table to match, and added a note explaining the naming split described below.

What was deliberately left alone

The RELEASE_KEYSTORE_PATH/RELEASE_KEYSTORE_PASSWORD/RELEASE_KEY_ALIAS/RELEASE_KEY_PASSWORD environment variable names inside the workflow jobs are untouched: app/build.gradle.kts's signingConfigs block reads those exact names via System.getenv(...), an internal contract between the workflows and Gradle that has nothing to do with the GitHub secret name and would gain nothing from renaming. RELEASE_PUSH_TOKEN is untouched too — its name already matched.

Test plan

  • Run build-apk.yml manually (workflow_dispatch) and confirm the release APK builds and is signed (the "Print release keystore SHA-1" step should show a real certificate, not fail on empty secrets).
  • Verify release.yml's next real run decodes the keystore and signs successfully before it touches main.

🤖 Generated with Claude Code

https://claude.ai/code/session_018zXVpxEbSWadqKyntXTXD6


Generated by Claude Code

The four Android signing secrets already exist in this repo under the
ANDROID_ prefix (ANDROID_KEYSTORE_BASE64, ANDROID_KEYSTORE_PASSWORD,
ANDROID_KEY_ALIAS, ANDROID_KEY_PASSWORD), but build-apk.yml and
release.yml still referenced them as secrets.RELEASE_*, a mismatch that
would make both workflows read empty secrets and fail signing at build
time.

Updated only the secrets.RELEASE_* -> secrets.ANDROID_* references (plus
one stale comment naming the old secret in prose) in both workflow
files. Left the RELEASE_KEYSTORE_PATH/RELEASE_KEYSTORE_PASSWORD/
RELEASE_KEY_ALIAS/RELEASE_KEY_PASSWORD environment variable names
untouched: app/build.gradle.kts's signingConfigs block reads those exact
names via System.getenv(), an internal contract between the workflows
and Gradle that has nothing to do with the GitHub secret name and would
gain nothing from renaming.

Updated docs/release-signing.md's secret-name table to match and added
a note explaining the ANDROID_*/RELEASE_* naming split, so the next
person following that doc doesn't recreate the same mismatch.

RELEASE_PUSH_TOKEN is untouched (name already matched).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018zXVpxEbSWadqKyntXTXD6
@Marcogn
Marcogn marked this pull request as ready for review September 6, 2026 07:50
@Marcogn
Marcogn merged commit 69284d9 into main Sep 6, 2026
1 check passed
@Marcogn
Marcogn deleted the claude/harmonize-android-secret-names branch September 6, 2026 07:50
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