The README sets out the listing each app keeps in its own repository, in the layout Google Play's tools read and
F-Droid accepts as it is: name, short and full description, icon, banner and phone screenshots, per language.
listing/banner.py draws an app's banner, the feature graphic Google Play asks for and the picture at the top of an
app's page in F-Droid: the app's mark in a round seal, its name and its address between two hairlines, on paper in
its own colours and typeface, 1024 by 500 pixels without transparency. banners.json holds the portal, "me-web?",
SimpleSchool and Passolo; the fonts are open-licence copies, listed in fonts/NOTICE.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W4YtEKqxKjKyHkFzuRVMNA
The commits since the previous tag of the same kind become notes.md, notes.txt, a
CHANGELOG.md of the last releases, an nfpm changelog for the deb and rpm, notes.json
and 500-character store notes; with release: 'true' they also go onto the tag's
release on the Releases tab, inside a marked block that leaves the rest of the text
alone. The same file reads the history from Gitea's API, for the packages publisher.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
play uploads an Android App Bundle to a track or moves a release between
tracks; apple uploads an iOS build for TestFlight and submits a version for
review. Each is one Python file over the store's own API, with openssl for
the signed tokens.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KizzWs2WQPWN2qgE7G6r8B