Commit graph

8 commits

Author SHA1 Message Date
e20549a094 Release 0.2.3+6 2026-08-30 17:52:06 +02:00
13cde4e96a Release 0.2.2+5 2026-08-30 17:42:46 +02:00
6dbc2e8c57 Release 0.2.1+4 2026-08-30 14:40:44 +02:00
f4a428f438 Release 0.2.0+3 2026-08-30 14:38:32 +02:00
15b7450c34 Release 0.1.1+2 2026-08-30 04:00:21 +02:00
1d5a23b7dc Release 0.1.0+1 2026-08-30 03:53:55 +02:00
397ef1d302 Release 0.1.0+1 2026-08-30 03:53:44 +02:00
Richard
2fc0981195 Somewhere for the app to look for a newer version of itself
Two static files behind nginx and a script that writes them. No
authentication: there is no account to check against, and the APK carries
no secret — the credential in that app is the addon URL, which lives in
the device keystore.

The APKs are committed rather than stored elsewhere. At ~34MB and a few
releases a year that beats standing up artifact storage for one app, and
the history is disposable because only the newest artifact is ever
fetched.

release.py reads the version out of amber-adult's pubspec instead of
taking it as an argument. A manifest advertising a build number the APK
does not carry is an update the device installs and is then offered
again, every launch, forever.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-30 03:53:38 +02:00