Modify release workflow for automated publication to app stores #19

Closed
opened 2026-07-01 03:15:02 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-07-01 03:15:02 +00:00 (Migrated from github.com)

Context

Automate publishing release artifacts to the app stores and archive prior binaries.

Scope

  • Release GitHub Actions workflow: build a signed AAB/APK on tag, with secure signing-key
    handling (keys in CI secrets, never in the repo).
  • Publish to Google Play (Play Publisher API) and Galaxy Store; provide the F-Droid path
    (metadata/tag — F-Droid builds itself).
  • Archive prior binaries to S3-compatible storage (versioned, checksummed bucket).
  • Release-notes/changelog generation; staged rollout where supported.
  • Keep the existing CI gate (assembleDebug / testDebugUnitTest / lintDebug) green as a
    prerequisite.

Acceptance criteria

  • Tagging a release builds, signs, publishes to the configured stores, and archives the
    binary; all secrets live in CI, not the repo.

Relevant files

  • .github/workflows/ (new release workflow alongside ci.yml)

Dependencies

Needs store accounts/listings (#16/#17/#18). Runs after the audit (#15).

## Context Automate publishing release artifacts to the app stores and archive prior binaries. ## Scope - [ ] Release GitHub Actions workflow: build a signed AAB/APK on tag, with secure signing-key handling (keys in CI secrets, never in the repo). - [ ] Publish to Google Play (Play Publisher API) and Galaxy Store; provide the F-Droid path (metadata/tag — F-Droid builds itself). - [ ] Archive prior binaries to S3-compatible storage (versioned, checksummed bucket). - [ ] Release-notes/changelog generation; staged rollout where supported. - [ ] Keep the existing CI gate (assembleDebug / testDebugUnitTest / lintDebug) green as a prerequisite. ## Acceptance criteria - Tagging a release builds, signs, publishes to the configured stores, and archives the binary; all secrets live in CI, not the repo. ## Relevant files - `.github/workflows/` (new release workflow alongside `ci.yml`) ## Dependencies Needs store accounts/listings (#16/#17/#18). Runs after the audit (#15).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: JMR-dev/LibreMail#19