Jean-Luc Makiola
9697b56404
Adds Play as a third channel alongside the F-Droid repo and the Codeberg download. It gets its own artifact: bundleRelease produces an AAB from the same source and signing config as the published APK, which is left untouched so the F-Droid reproducibility guarantee is unaffected. The upload runs as a separate trailing job rather than more steps in 'release'. Play is the only channel that can reject a good build for reasons the pipeline cannot see — listing rules, policy review, a track needing manual promotion — and that must surface as one red job beside a release that already shipped, not as a failure of the workflow that shipped it. It also skips cleanly until PLAY_SERVICE_ACCOUNT_JSON exists, so the pipeline keeps working during Play Console setup. fastlane is scoped deliberately to 'supply'. Build and signing stay on Gradle: interposing fastlane there would add a layer able to inject flags into the one build a third party verifies byte-for-byte. What fastlane buys is that fastlane/metadata/android — already the source F-Droid harvests — is exactly what supply consumes, so 'What's New' comes from CHANGELOG.md via the existing sync script for both stores. Listing text is not pushed per release (an accidental overwrite of a live listing is a policy-review event, not a revert), and images are skipped because the committed assets satisfy F-Droid but not Play: the screenshots are 1280x2856 with alpha where Play caps the long edge at 2x the short edge and wants 24-bit, and no 1024x500 featureGraphic exists. The job runs without a container image despite fastlane publishing one: act_runner provides no node inside custom job containers, so checkout and download-artifact cannot run there. Uploads default to the internal track — promotion to production stays a human action, matching the rule that UI releases wait for on-device review. Note that Play App Signing means Play installs and F-Droid installs carry different signatures and cannot update each other; the release key is registered only as the upload key. Documented in docs/RELEASING.md.
Calendula
A modern Material 3 Expressive calendar for Android.
Reads, writes, and reminds — on top of the system calendar, with zero network access.
Calendula is named after the flower whose name — like the word calendar —
comes from the Latin kalendae, the first day of the month. It lives
entirely on top of Android's CalendarContract: any calendar synced to your
device (CalDAV via DAVx5, Google, local, WebCal subscriptions, …) simply
appears, and everything you create or edit syncs back the same way. No own
database, no sync stack reinvented.
✨ Features
Calendar
- Month, week, and day views with a one-tap view switcher
- Full event details — attendees and their responses, reminders, recurrence (humanized), availability, visibility, foreign time zones
- Per-calendar visibility toggle, grouped by account
Editing
- Create, edit, and delete events — including recurring events with scoped writes: only this event, this and all following, or the whole series
- Recurrence picker with one-tap presets and custom rules (interval, weekday toggles, end conditions); rules it can't express are preserved verbatim
- Conflict-safe saves: if an event changed elsewhere while you were editing, Calendula asks instead of silently overwriting
- Read-only calendars (WebCal, birthdays) are detected and respected
Reminders
- Event reminders delivered by Calendula itself as notifications — essential when it's your only calendar app, since Android delegates reminder delivery to calendar apps
- Tap a reminder to land on the event
Design & privacy
- Real Material 3 Expressive throughout — dynamic color (Android 12+), expressive motion and shapes, light/dark theme
- German and English UI, per-app language setting — and open to community translations
- Zero telemetry, zero analytics, no internet permission — your data never leaves the device
📦 Install
F-Droid (recommended)
Calendula is on the official F-Droid repository — just search for Calendula in any F-Droid client, or install it from f-droid.org.
Self-hosted repo (latest builds)
New versions are built, signed, and published to a self-hosted repository the moment each tag lands — usually a few days ahead of the official repo, which rebuilds on F-Droid's own schedule. Add it for the freshest builds:
-
In your F-Droid client, open Settings → Repositories → Add (or open the link below on your phone):
https://apps.dev.jeanlucmakiola.de/dev/fdroid/repo?fingerprint=C2C0640402BF458FC0ED957AF0B37AA4C14022E72F89CE90B5965B458CF73425Repo:
https://apps.dev.jeanlucmakiola.de/dev/fdroid/repo· fingerprint (SHA-256):C2C0 6404 02BF 458F C0ED 957A F0B3 7AA4 C140 22E7 2F89 CE90 B596 5B45 8CF7 3425 -
Refresh, search for Calendula, install.
Both channels share the same signing key, so you can switch between them without reinstalling. Or build from source — see below.
📚 Documentation
- Building from source — requirements and Gradle tasks
- Architecture — the layered design and key pipelines
- Roadmap — what's shipped and what's next
🌍 Translations
Calendula ships in German and English, and you're warmly invited to add your language. Translations are managed on a self-hosted Weblate:
No coding needed — register on the Weblate server, pick (or request) a language, and translate the strings in your browser. You can also reach this link in the app from the top of Settings → App language.
📜 License
MIT — Jean-Luc Makiola, 2026