Correct what the listing refetch actually buys

The docstring claimed a description corrected upstream without a new release
still lands here. It does not: the fastlane tree is read from the source
archive at the released tag, so an edit on main is invisible until the tag
moves or a new release is cut. Says so now, since that is the thing someone
reaching for this function wants to know.

Comment only; no behaviour change, so nothing to redeploy.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
randogoth 2026-10-14 12:49:16 +03:00
parent 5c1c9d1608
commit cc0f06eb7d

View file

@ -282,11 +282,17 @@ _listing_done = {}
def sync_listing(app, cfg, tag, apk: Path, locale): def sync_listing(app, cfg, tag, apk: Path, locale):
"""Refresh metadata/<packageId>/ from the app repo. True if it changed. """Refresh metadata/<packageId>/ from the app repo. True if it changed.
Refetched on every run rather than only when the release moves, so a Read from the source archive at the *released tag*, not from the default
description or screenshot corrected upstream without a new release still branch, so the listing always describes the build it ships with. The
lands here. Within a run it is done once per tag: the later passes exist to consequence is worth stating plainly: correcting a typo in
notice a *new* release, and repeating the fetch and the APK icon parse for full_description.txt on main changes nothing here. It takes a new release,
a tag already handled would be pure waste. or moving the tag.
Refetched on every run even when the release has not moved, so a tag that
was moved in place is still picked up, and so a listing lost to a failed
run repairs itself. Within a single run it is done once per tag: the later
passes exist to notice a *new* release, and repeating the fetch and the APK
icon parse for a tag already handled would be pure waste.
""" """
if _listing_done.get(app["id"]) == tag: if _listing_done.get(app["id"]) == tag:
return False return False