From 8a804785558c60faa558b8670f92a13687e04ebf Mon Sep 17 00:00:00 2001 From: Jean-Luc Makiola Date: Sun, 21 Jun 2026 12:33:55 +0200 Subject: [PATCH] docs(architecture): describe merge-driven release flow Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/ARCHITECTURE.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 6bd2b04..21d1f42 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -143,5 +143,6 @@ JUnit 5 + Truth + Turbine on the JVM. The seams that make it work: `CalendarDataSource` is faked (`FakeCalendarDataSource` records writes), mappers parse `ColumnReader`/plain maps instead of cursors, domain logic (recurrence, validation, snapshots, write-value building) is pure. CI -(Gitea Actions) runs `lint test assembleDebug` on every push; release tags -additionally build, sign, and publish to the self-hosted F-Droid repo. +(Gitea Actions) runs `lint test assembleDebug` once per pull request; merging a +bumped `versionName` to `main` builds, signs, and publishes to the self-hosted +F-Droid repo and then mints the `vX.Y.Z` tag + release. See docs/RELEASING.md.