RobotAutomationDevelopment-Dept/Ubisam-MobileGit
16
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Ubisam-MobileGit/tasks/070-update-from-gitea.md
choiminyeong 137480f30d TASK-076: version 0.2.5, published as the release build 
The release build type is signed with the key the published builds have had,
so it installs over them.

Agent: main (opus)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 18:17:38 +09:00

2.5 KiB
Raw Permalink Blame History

TASK-070: The app's update check and download use the team's Gitea

Status: implemented; required checks pass; not yet seen on a device Owner: Claude Reviewer: human product owner

Request

The update notice in the app opened the old download page, which asks for a password. The product owner no longer uses that page (2026-10-12) and asked for the app to use the Gitea link instead.

Outcome

  • The app reads the newest version from version.json on the apk branch of RobotAutomationDevelopment-Dept/Ubisam-MobileGit, and "download" opens UBGitea.apk on that branch. Neither asks for a password or a sign-in.
  • The wording no longer mentions a password or a download page.

Scope

  • Included: the two addresses, the wording, version.json on the apk branch.
  • Follow-up (product owner, 2026-10-12: the old site is not used any more): tools/publish-download.py, which built the old page, is removed. Nothing in the repository points at the old site now.
  • Excluded: the choimy0204.github.io/ubgitea/ page itself. It is in another repository and is left as it is.

Writable paths

  • app/src/main/java/com/ubisam/ubgitea/core/update/AppUpdate.kt
  • app/src/main/java/com/ubisam/ubgitea/MainActivity.kt
  • app/src/main/res/values/strings_update.xml
  • tools/publish-download.py (removed)
  • tasks/066-download-page-and-update-check.md
  • tasks/070-update-from-gitea.md
  • docs/development-log.md

Acceptance criteria

  • No address of the old page is left in the app.
  • version.json is on the apk branch and names the APK that is there.
  • Seen on a device: the notice appears for a newer build and "download" fetches the APK.

Security and privacy

The two addresses are public and are fetched with a client that carries no Gitea token. The repository being public was the product owner's choice in TASK-067.

Publishing a build from now on

  1. Raise versionCode and versionName in app/build.gradle.kts, then assembleRelease (the release build since 0.2.5, TASK-076; assembleDebug before that).
  2. On the apk branch, replace UBGitea.apk and set version.json to the same version.
  3. Push the apk branch.

Copies installed before this task still read the old page's version.json, so they are never told about a build published here; they need one install by hand from the Gitea link.

Required checks

./gradlew compileDebugKotlin compileDebugUnitTestKotlin testDebugUnitTest assembleDebug lintDebug

Evidence

See the development log entry for TASK-070.

Review findings

None yet.