Skip to content

ci(workflow): inject keystore signing properties into apk build (AI-generated) - #178

Merged
GiZano merged 1 commit into
mainfrom
ci/inject-android-signing
Oct 17, 2026
Merged

GiZano merged 1 commit into
mainfrom
ci/inject-android-signing

Conversation

@GiZano

@GiZano GiZano commented Oct 17, 2026

Copy link
Copy Markdown
Member

This pull request description was written by an AI agent.

Description

Updates the Android APK build workflow (build-apk.yml) to sign release builds using Gradle injected properties:

  • Decodes the KEYSTORE_BASE64 secret into release.keystore in the project root prior to building.
  • Injects Android signing parameters (-Pandroid.injected.signing.store.file, -Pandroid.injected.signing.store.password, -Pandroid.injected.signing.key.alias, -Pandroid.injected.signing.key.password) into ./gradlew assembleRelease using environment variables populated from GitHub Secrets.

Testing Instructions

  1. Verify workflow syntax and formatting (npx prettier --check .github/workflows/build-apk.yml).
  2. Verify release.keystore generation and Gradle signing resolution in CI runs.

Checklist

  • My code follows the guidelines in CONTRIBUTING.md.
  • I have run npm run lint and npx tsc --noEmit and there are no errors.
  • My changes do not introduce unnecessary complex UI libraries.

AI Generation Disclosure

  • Was AI used to generate code in this PR? Yes
  • If Yes, which tool/model? Antigravity (Google DeepMind) / Gemini 3.8 Flash
  • Files or line ranges generated by AI:
    • .github/workflows/build-apk.yml (lines 40-56)

…enerated)

- Decode KEYSTORE_BASE64 secret into release.keystore
- Pass signing configuration to assembleRelease via Gradle project properties
@codecov

codecov Bot commented Oct 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@GiZano
GiZano merged commit 24ecfec into main Oct 17, 2026
4 checks passed
@GiZano
GiZano deleted the ci/inject-android-signing branch October 17, 2026 09:43
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