Update and release delivery: tracking issue #57

Open
opened 2026-09-05 15:11:14 +00:00 by ImBenji · 0 comments
Owner

Umbrella issue. lib/update/ is ~470 lines with no board presence.

What exists: app_version.dart (a YYYY-N[channel] scheme with alpha/beta/rc/stable ordering and comparison), update_check_service.dart, and download_install_service.dart which picks the right platform binary out of the latest Gitea release for the web-only download-and-install menu item. Platform detection is split across download_platform.dart / _parser / _stub / _web. Covered by app_version_test, download_install_service_test, download_platform_test.

Adjacent context already captured in memory rather than on the board, worth folding in here:

  • release builds cover Android, macOS, Windows and Linux; web is deploy-on-push and not a release artifact
  • re-running a Gitea release workflow replays the OLD commit and OLD workflow file, so a moved tag needs the release recreating
  • Android CI cannot self-host on infras-1 (measured OOM even at a 2 GB heap) and lives on Codemagic, where an unpinned Flutter stable means a new Gradle floor can break the build with no code change

Use this for update/release work that does not warrant its own issue.

Opened during the roadmap audit on 2026-09-05.

Umbrella issue. `lib/update/` is ~470 lines with no board presence. What exists: `app_version.dart` (a `YYYY-N[channel]` scheme with alpha/beta/rc/stable ordering and comparison), `update_check_service.dart`, and `download_install_service.dart` which picks the right platform binary out of the latest Gitea release for the web-only download-and-install menu item. Platform detection is split across `download_platform.dart` / `_parser` / `_stub` / `_web`. Covered by `app_version_test`, `download_install_service_test`, `download_platform_test`. Adjacent context already captured in memory rather than on the board, worth folding in here: - release builds cover Android, macOS, Windows and Linux; web is deploy-on-push and not a release artifact - re-running a Gitea release workflow replays the OLD commit and OLD workflow file, so a moved tag needs the release recreating - Android CI cannot self-host on infras-1 (measured OOM even at a 2 GB heap) and lives on Codemagic, where an unpinned Flutter stable means a new Gradle floor can break the build with no code change Use this for update/release work that does not warrant its own issue. Opened during the roadmap audit on 2026-09-05.
ImBenji added this to the Arcs & Angles project 2026-09-05 15:11:14 +00:00
ImBenji added the enhancement label 2026-09-05 15:13:50 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IMBENJI.NET/Metro-Map-Maker#57