Skip to content

ci(mobile): publish APK release metadata - #5

Open
g4st3r-d3v wants to merge 1 commit into
mainfrom
feature/apk-distribution
Open

g4st3r-d3v wants to merge 1 commit into
mainfrom
feature/apk-distribution

Conversation

@g4st3r-d3v

Copy link
Copy Markdown
Contributor

Summary

  • Update the manual Android APK workflow to publish APKs to S3 as releases/<run_number>/app.apk.
  • Write releases/latest-android.json with version, size, run, commit, bucket, and APK key metadata for the Telegram bot PR.
  • Keep Android versionCode driven by github.run_number via ANDROID_VERSION_CODE.

Validation

  • pnpm typecheck
  • pnpm test:smoke
  • pnpm test
  • actionlint .github/workflows/build-android-apk.yml
  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/build-android-apk.yml")'

Notes

  • Local EAS build was not run; this workflow requires repository secrets and is intended to be verified by GitHub Actions workflow_dispatch after merge.
  • APK size will be known after the first successful EAS build uploads metadata.

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