release: cut v2.4.0 — per-event colors
All checks were successful
CI / ci (push) Successful in 9m20s
Release — F-Droid repo + Gitea release / build-and-deploy (push) Successful in 9m22s
Release — F-Droid repo + Gitea release / ci (push) Successful in 2m3s
Release — F-Droid repo + Gitea release / gitea-release (push) Successful in 7s
All checks were successful
CI / ci (push) Successful in 9m20s
Release — F-Droid repo + Gitea release / build-and-deploy (push) Successful in 9m22s
Release — F-Droid repo + Gitea release / ci (push) Successful in 2m3s
Release — F-Droid repo + Gitea release / gitea-release (push) Successful in 7s
Optional per-event color in the event form. The read/render path already resolved EVENT_COLOR with a calendar fallback; this adds the write side and the picker. - Palette-backed calendars (Google, some CalDAV) pick from the account's Colors (TYPE_EVENT) and write EVENT_COLOR_KEY, so the color round-trips through sync; local calendars write a raw EVENT_COLOR from the shared CALENDAR_COLOR_PALETTE. Never writes a raw color to a palette calendar. - Swatch row + palette extracted to ui/common/ColorSwatchRow.kt (shared with the calendar editor). Switching calendars resets the choice (keys are account-scoped); a "Reset" action returns to the calendar color. - New "Allow colors on unsupported calendars" setting (off by default) extends the raw path to no-palette synced calendars, with an honest "may not survive sync" warning on the picker and in Settings. - Color flows through insert / dirty-checked update / occurrence-exception; mapper, form, and repository tests added. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
17
CHANGELOG.md
17
CHANGELOG.md
@@ -7,6 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
## [2.4.0] — 2026-06-17
|
||||
|
||||
### Added
|
||||
- Per-event colors: give a single event its own color, instead of always
|
||||
inheriting its calendar's. Add the new "Color" field from "More fields" in
|
||||
the event form. On calendars that publish their own color set — such as
|
||||
Google — you pick from that calendar's palette, so the color is stored
|
||||
with the event and shows correctly on every synced device. On local
|
||||
calendars you pick from Calendula's palette. "Reset" returns an event to
|
||||
its calendar's color
|
||||
- A new "Allow colors on unsupported calendars" setting (New event form,
|
||||
off by default) extends per-event colors to calendars that publish no
|
||||
color set of their own (some CalDAV). Such a color is kept on the device
|
||||
and may be dropped or overwritten on that calendar's next sync — a
|
||||
limitation of those calendars, called out plainly in the setting and on
|
||||
the color picker
|
||||
|
||||
## [2.3.0] — 2026-06-16
|
||||
|
||||
### Changed
|
||||
|
||||
Reference in New Issue
Block a user