12 Commits
Author SHA1 Message Date
waozi b8bfb7ff1c Reuse fixed release-ready outputs and one shared build cache
Custom RELEASE_READY_OUTPUT names now map to build/release-ready, and
only build/release-ready-phone keeps a separate purpose, so task and
version names no longer leave a new folder per run. Both share
build/release-ready/home under an exclusive cache lease held through
container exit. The release command uses the same mapping. Phone
installs take a lock, select only an APK this run built and reuse the
default signed path. Nothing prunes existing output.
2026-11-01 18:41:58 -03:00
waozi 28788c067a Show Lumi's update notes and Play release notes in the user's language
Lumi announced each update in English whatever the language. Translations
of a release now live in locales/changelog/LANGUAGE.md beside the English
CHANGELOG.md; the build packs them as release-notes-LANGUAGE.json, Lumi
picks the active language's notes for the same release, and
update_version.sh writes each Play listing's notes. A test requires every
language to translate the newest release, and the fonts cover them.

Shorten the 2.1.61 notes.
2026-10-29 12:21:05 -03:00
waozi a78d7d43c4 Keep scripts/release.py executable 2026-10-27 03:04:31 -03:00
waozi 16161e4482 Let make release read a separate release-ready run
RELEASE_READY_OUTPUT names the run's outputs, as in release-ready.sh.
2026-10-27 03:03:46 -03:00
waozi 32a4fe7951 Record the trusted reference for fixed release publication 2026-10-27 01:55:28 -03:00
waozi 434c99f697 Rename bundled app sources and build targets from cells to apps 2026-10-24 23:17:45 -03:00
waozi 2e8d852a93 Release tested commits without blocking ongoing development 2026-10-22 22:18:11 -03:00
waozi 77f90eb61a Keep Tai Chi data distinct from executable binaries and record the owner Moto waiver 2026-10-22 15:47:16 -03:00
waozi 1cb38ece5c Record new phone receipts without taking unrelated changes 2026-10-22 06:33:09 -03:00
waozi bb006dcac6 Build only the target phone architecture during release checks 2026-10-22 04:19:06 -03:00
waozi 1a30ab32b2 Keep late release-note edits in the final unpushed release commit 2026-10-20 16:45:13 -03:00
waozi 1388441cf5 Make a release one final commit with make release-ready and make release
Last week a release needed a commit for every phone check and CI repair:
the release commit came first, then fixes, then "Record" commits, and CI
went red after phone checks because it only ran on GitHub.

make release-ready runs CI's checks before pushing: in the Test job's
Ubuntu 24.04 with its apt packages (.github/local-ci/Containerfile), on
HEAD's committed content with the locked packages, through an overlay of
this checkout so nothing reaches the working tree. It covers Secret Scan,
package URLs, the large-file guard, make test, make visual-test and make
package-compat-test, and records a stamp for that content.

make release then, with the development Moto connected, refuses
uncommitted app files and package overrides that are not clean on the
lock, syncs ./update_version.sh output, requires the release-ready stamp
for this content, builds the debug APK for the phone's ABI, runs the phone
check and makes the one "Release Inner Breeze X.Y.Z" commit with the
receipt. After a late fix, running it again moves the unpushed release
commit above the fix (commits are replayed with merge-tree; only refs
move) instead of adding another. It never pushes or tags.
2026-10-17 17:53:16 -03:00