You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: migrate no_scheduling legacy flags to new 'scheduling' feature
Replace the old_flags no_scheduling / no_scheduling_mailbox /
no_scheduling_calendar_user_address_set with the new 'scheduling'
feature entry in the compatibility matrix, and adapt the test code to
use skip_unless_support("scheduling") / is_supported("scheduling").
Servers with no_scheduling → "scheduling": {"support": "unsupported"}:
xandikos_v0_2_12, xandikos, radicale, robur, posteo, purelymail
Servers with partial scheduling (mailbox/address-set missing) → noted
with a TODO for future sub-features: gmx
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
## was apparently observed working for a while, possibly due to the master/more_checks split-brain git branching incident in the server-checker project.
1453
1439
## unsupported in be26d42b1ca3ff3b4fd183761b4a9b024ce12b84 / 537a23b145487006bb987dee5ab9e00cdebb0492 2026-02-19. Supported when testing again short time after. Either I'm confused or it's "fragile".
0 commit comments