release: v2.8.0 #34
Reference in New Issue
Block a user
Delete Branch "release/v2.8.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cuts v2.8.0. Merging this to
maintriggersrelease.yaml, which buildsthe committed
versionName(2.8.0 / code 20800), publishes to F-Droid, andmints the
v2.8.0tag + Gitea release.Highlights
Also
Release prep
versionName2.7.5 → 2.8.0,versionCode→ 20800.[Unreleased]→[2.8.0] — 2026-06-23.fastlane/.../changelogs/20800.txt.Verification
releaseTest(R8-minified) built and verified on-device from a clean first-run state — no issues.🤖 Generated with Claude Code
Attendees were read-only (shown on the detail screen since v0.6) but the form couldn't write them — the last read-only gap in the event model. Add a Guests section to the create/edit form: - Inline grouped list: each guest is a tonal card (avatar, name/email, a tappable Required/Optional role chip, remove); the trailing card is an inline email field — type an address, press Done, it commits. No dialog, matching the app's inline-field input idiom. Manual adds are email-only (names come from sync); the InlineTextField gains IME-action support. - Reminders restyled to the same grouped-list pattern (shared GroupedItemCard / AddActionCard), replacing the single-card blob. Persistence (CalendarDataSource): new guests are written as plain RELATIONSHIP_ATTENDEE / STATUS_INVITED rows — no fabricated organizer. On edit, a dirty-checked reconcileAttendees diffs by email: drops removed guests, inserts new ones, updates only the required/optional flag on kept rows (preserving response status). Organizer, resources and no-email rows are never touched. toEditForm carries only editable guests, so attendees now ride in the edit snapshot and an external guest change trips the conflict check. Per the settled invitation decision: Calendula has no INTERNET and never sends an invitation — it only writes the rows; the backend decides delivery. The section shows honest, calendar-aware copy ("your account may email guests when it syncs" on synced calendars, "no one is notified" on local). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>