Publish pre-built APK on release tags; refresh README for Mobile Tunnel launch

Merged
MI
2d ago
+92-1

Summary

Launch traffic lands on this repo, but the only install path today is building with Gradle. This adds a release workflow so every v* tag publishes a downloadable APK, and updates the README to match the "Mobile Tunnel" launch.

Changes

  • .github/workflows/release.yml: on a v* tag (or manual run with a tag), builds assembleDebug and creates a GitHub release with sealgate-mobile-tunnel-<tag>-debug.apk attached. The debug build is the only variant CI can sign without release keys that keeps computer control, which the drone demo needs.
  • Optional DEBUG_KEYSTORE_BASE64 secret: if set, all releases share one signing key so users can upgrade in place. Without it, each release is signed with a fresh key and upgrading requires uninstalling first.
  • .github/release-notes.md: release body explaining this is a debug build and that computer control is opt-in (in-app toggle plus Android Accessibility setting).
  • README: retitled SealGate Mobile Tunnel (mobile-stdiod kept as subtitle), "Just want to try it?" link to the latest release, and a drone demo section with reproduce steps.

After merge, push v0.1.0 to cut the first release.

Testing

  • Build passes (./gradlew assembleDebug): via Android CI on this PR (no SDK in the authoring sandbox)
  • Unit tests pass (./gradlew testDebugUnitTest): via Android CI
  • Lint passes (./gradlew lintDebug): via Android CI
  • actionlint clean on release.yml
  • Release workflow itself only runs on a tag, so first real run is v0.1.0

Related Issues

None.

šŸ¤– Generated with Claude Code

https://claude.ai/code/session_01TBPcx6o1GWKvqRkUc9Qkyk


Generated by Claude Code


Summary by cubic

Adds a release workflow so every v* tag publishes a downloadable APK, and refreshes the README for the SealGate Mobile Tunnel launch. Until now, the only install path was building with Gradle.

Release workflow

  • Waits for a v* tag, then builds assembleDebug and attaches sealgate-mobile-tunnel-<tag>-debug.apk to a GitHub release; debug is the only variant CI can sign without release keys that still includes computer control.
  • Fails the build if the tag does not match versionName in app/build.gradle.kts.
  • Setting the DEBUG_KEYSTORE_BASE64 secret (standard debug credentials: store/key password android, alias androiddebugkey) shares one signing key across releases so users can upgrade in place; otherwise each release uses a fresh key and upgrading requires uninstalling first.
  • Release notes state this is a debug build and that computer control is opt-in (app toggle plus Android Accessibility setting).

README

  • Retitles the project SealGate Mobile Tunnel, points "Just want to try it?" at the latest release, and adds a drone demo section with the steps to reproduce it.

After merge, push v0.1.0 to cut the first release.