coffey-labs/ihasmail
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 2 Wiki Activity

Credit the testing to 0.16.22, where it was done

Browse Source 
The live instance was tested on 0.16.22, not only read against its diff. The
badge says tested against it again, and 0.16.21 becomes the release before.
This commit is contained in:
jcoffey-dev
2026-09-13 17:50:43 -07:00
parent 28acad6865
commit 64dbb30e70
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -7
View File
@@ -9,7 +9,7 @@
<p align="center"> <p align="center">
<a href="LICENSE"><img alt="Licence: AGPL-3.0-or-later" src="https://img.shields.io/badge/licence-AGPL--3.0--or--later-2dd4bf?style=flat-square"></a> <a href="LICENSE"><img alt="Licence: AGPL-3.0-or-later" src="https://img.shields.io/badge/licence-AGPL--3.0--or--later-2dd4bf?style=flat-square"></a>
<a href="https://stalw.art" target="_blank" rel="noreferrer"><img alt="Requires Stalwart 0.16 or newer; runs on 0.16.22" src="https://img.shields.io/badge/Stalwart-0.16.22-6366f1?style=flat-square"></a> <a href="https://stalw.art" target="_blank" rel="noreferrer"><img alt="Requires Stalwart 0.16 or newer; tested against 0.16.22" src="https://img.shields.io/badge/Stalwart-0.16.22-6366f1?style=flat-square"></a>
<a href="https://docs.ihasmail.org" target="_blank" rel="noreferrer"><img alt="Documentation: docs.ihasmail.org" src="https://img.shields.io/badge/docs-docs.ihasmail.org-0ea5e9?style=flat-square"></a> <a href="https://docs.ihasmail.org" target="_blank" rel="noreferrer"><img alt="Documentation: docs.ihasmail.org" src="https://img.shields.io/badge/docs-docs.ihasmail.org-0ea5e9?style=flat-square"></a>
<a href="https://coffeylabs.org" target="_blank" rel="noreferrer"><img alt="by Coffey Labs" src="https://img.shields.io/badge/by-Coffey%20Labs-0f766e?style=flat-square"></a> <a href="https://coffeylabs.org" target="_blank" rel="noreferrer"><img alt="by Coffey Labs" src="https://img.shields.io/badge/by-Coffey%20Labs-0f766e?style=flat-square"></a>
</p> </p>
@@ -88,9 +88,9 @@ wrong guess had somewhere to fall back to, so it failed *quietly* — and that
reached production. With one supported generation a wrong guess is a loud error reached production. With one supported generation a wrong guess is a loud error
on the first call. on the first call.
**The live instance runs 0.16.22**, released 13 September 2026 and upgraded to **Validated against 0.16.22**, released 13 September 2026: the live instance
the same day. It was read against its diff rather than re-run, and four of its runs it and the app has been tested against it. Four of its JMAP changes are
JMAP changes are visible to a client, all in calendars and contacts: visible to a client, all in calendars and contacts:
`CalendarEvent/get` returns `baseEventId` only on a synthetic occurrence, so a `CalendarEvent/get` returns `baseEventId` only on a synthetic occurrence, so a
one-off event now carries `null` there; it returns `null` for `recurrenceRule` one-off event now carries `null` there; it returns `null` for `recurrenceRule`
and `recurrenceOverrides` asked for on an occurrence; `useDefaultAlerts` is and `recurrenceOverrides` asked for on an occurrence; `useDefaultAlerts` is
@@ -98,9 +98,9 @@ stored per user and reads `false` when never set; and `CalendarEvent/get` and
`ContactCard/get` return only `id` for an empty `properties` list, rather than `ContactCard/get` return only `id` for an empty `properties` list, rather than
everything. The mock does not follow these yet. everything. The mock does not follow these yet.
**Validated by hand against 0.16.21**, released 6 September 2026: the app was Before it, **0.16.21**, released 6 September 2026: the app was run against a
run against a real instance of it and the mail, calendar and contacts paths were real instance of it and the mail, calendar and contacts paths were exercised by
exercised by hand. Four of that release's JMAP changes are visible to a client hand. Four of that release's JMAP changes are visible to a client
— an occurrence of a recurring event is now identified by its recurrence id — an occurrence of a recurring event is now identified by its recurrence id
rather than by its position in the series, so an id held across a write no rather than by its position in the series, so an id held across a write no
longer silently names a different date; `Calendar/get` and `AddressBook/get` longer silently names a different date; `Calendar/get` and `AddressBook/get`