feat/mobile-live-update #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/mobile-live-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
- arm64 Mac: warn instead of block (Rosetta 2 works) - Fix all Authorization headers to use ${FORGEJO_TOKEN} variable - Fix indentation issues causing syntax errors - Add cleanup for copied app-release.apk - Support unsigned APK on arm64 builds- Add MobileAppVersion model with platform, version, urls, mandatory flag - Add POST /api/v1/mobile/app-version (create) - Add PUT /api/v1/mobile/app-version/{platform} (update) - Add GET /api/v1/mobile/app-version/{platform} (get latest) - Alembic migration for mobile_app_versions table - Deploy script now updates DB after Forgejo releaseBackend: - MobileAppVersion model with platform, version, build_number, URLs, is_active, is_mandatory - Admin API: CRUD endpoints at /api/v1/admin/official-data/mobile-app-version - Public API: GET /api/v1/mobile/app-version/{platform} for frontend/mobile Frontend: - AdminOfficialDataView: Mobile Version section with summary card (single active version) - Uses activeVersion computed (finds is_active or first) - Create/Edit dialog with all fields - MobileDownloadView: fetches version from backend API, fallback to Forgejo - Single 'Copier le lien' button, direct download opens in new tab - QR code uses dynamic URL from backend Deploy script: - After Forgejo release, POSTs to backend API to update DB - Auto-deletes existing local/remote tags before push - Builds debug APK (signed) for direct install- Mobile app version endpoints now declared before catch-all /{entry_id} - Admin API /mobile-app-version works correctly