Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,19 @@ This release works with caldav 3.7.0: the tester carries the definitions of the
- **`save-load.todo.status`**, **`save-load.todo.status.rfc10051`** and **`save-load.todo.priority`** - which STATUS values (RFC 5545's four; PENDING and FAILED from RFC 10051 apart) and which PRIORITY values (0 to 9) a task keeps, with the extra keys `values`, `map` and `refused`. Ox drops PENDING and FAILED and keeps priorities 1, 5 and 9 only; Zimbra stores PENDING and FAILED as NEEDS-ACTION and refuses CANCELLED. PRIORITY:0 dropped is `full`: no PRIORITY means the same.
- **`supported-task-modes`** - whether the server advertises RFC 10051 with `CALDAV:supported-task-mode-set` on the calendar home or a calendar. Neither Ox nor Zimbra does, and the RFC 10051 status verdict says so.
- **`save-load.icalendar.x-parameter`** - whether an X- parameter on SUMMARY is stored, in an event and then in a task. Ox and Zimbra drop it from the event.
- **`save-load.todo.alarm`** - whether a task's VALARM is stored as sent: its ACTION, its relative TRIGGER and its DESCRIPTION. Ox keeps it, but makes the TRIGGER absolute and replaces the DESCRIPTION with "Open-XChange" (`broken`, the behaviour saying what changed); it keeps an event's VALARM as sent. caldav does not define this feature yet, so the tester adds its definition itself until a caldav release has it.
- **`save-load.event.recurrences.rdate`** - whether an event's RDATE is stored. Zimbra drops every RDATE, and keeps an RRULE. caldav does not define this feature yet, so the tester adds its definition itself until a caldav release has it.
- **`multiget.deleted`** - whether a calendar-multiget answers a deleted object as missing. Zimbra still returns its data, while a GET answers 404.
- **`save-load.stable-url`** also stores a task under a name that is not its UID, and records `uid_ics_components: [VTODO]` where only the task is renamed `<uid>.ics` (Ox).
- **`save-load.icalendar.olson-tzid`** - whether an event with `TZID=Asia/Tokyo` and no VTIMEZONE is placed in Tokyo time, judged by time-range searches in UTC; the behaviour says whether the server adds a VTIMEZONE of its own. Where `full`, a client may leave the VTIMEZONE out. caldav does not define this feature yet, so the tester adds its definition itself until a caldav release has it. See https://github.com/python-caldav/caldav/issues/849.
- **`save-load.icalendar.olson-tzid`** - whether an event with `TZID=Asia/Tokyo` and no VTIMEZONE is placed in Tokyo time, judged by time-range searches in UTC; the behaviour says whether the server adds a VTIMEZONE of its own. Where `full`, a client may leave the VTIMEZONE out. The event is compared with the same event carrying its VTIMEZONE and with one at 12:00 UTC, so a search that misplaces zoned times or only matches start times does not stop the probe from reaching a verdict. caldav does not define this feature yet, so the tester adds its definition itself until a caldav release has it. See https://github.com/python-caldav/caldav/issues/849.
- **`search.time-range.event.overlap`** and **`search.time-range.todo.overlap`** - whether a time-range search finds an event or task that overlaps the range without starting inside it (RFC 4791 section 9.9): one range inside the object, one straddling its end. Robur only finds events whose DTSTART is in the range, Cyrus and GMX only tasks whose DTSTART is.
- **`search.time-range.event.tzid`** - whether a time-range search places an event with `TZID=Asia/Tokyo` and its VTIMEZONE at its time in UTC. Infomaniak finds it only by a range that also reaches 12:00 UTC, its local time read as UTC. caldav does not define these three features yet, so the tester adds their definitions itself until a caldav release has them.

### Fixed

- A probe for a feature the installed caldav does not know no longer aborts the whole run. The check logs a warning and loses that feature only, and a check reading it gets "unknown"; a check with no other feature is not run.
- **`save.duplicate-uid.cross-calendar`** - whether saving the copy moved the original is read from a listing of the original calendar, not from a search by UID, which a stale search index answers wrongly.
- **`save.if-none-match`** also puts an object with another UID under a taken name, as a new object saved there would have one: Bedework (3 and 5) refuses the same UID with 412, but another one with 500, which the library does not read as "exists". It is now `ungraceful` there.

## 1.8.0 - 2026-10-30

Expand Down
Loading
Loading