14 Commits
Author SHA1 Message Date
waozi 434c99f697 Rename bundled app sources and build targets from cells to apps 2026-10-24 23:17:45 -03:00
waozi b2126cfac2 Point source, release and update links at github.com/waozixyz/breeze 2026-10-23 11:54:46 -03:00
waozi 6fd9ed80db Keep git maintenance out of the temporary repositories tests remove 2026-10-23 04:36:10 -03:00
waozi b0e206ae13 Leave the visual suites out of CI and the release checks
make visual-test still runs them locally.
2026-10-23 02:39:36 -03:00
waozi b532496100 Run the release and package workflows when their tests are repaired 2026-10-23 00:11:07 -03:00
waozi ea55b0f5cf Preserve fixed-source CI checks when master advances 2026-10-22 23:33:33 -03:00
waozi 000415628f Require matching green CI before promoting checked release artifacts 2026-10-22 23:25:53 -03:00
waozi b8d4171e6e Reuse fully verified release artifacts when only the phone receipt changes 2026-10-22 23:19:03 -03:00
waozi f83b44fd3e Recover corrupt Android SDK downloads and start release builds earlier 2026-10-22 22:43:10 -03:00
waozi 2e8d852a93 Release tested commits without blocking ongoing development 2026-10-22 22:18:11 -03:00
waozi 43131468fa Preserve practice session details and restore account navigation 2026-10-22 19:50:02 -03:00
waozi 1cb38ece5c Record new phone receipts without taking unrelated changes 2026-10-22 06:33:09 -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