Merge upstream sabre-io/vobject master 2026-05-31 (4.6.0)

[willaix]

What

Syncs our fork with upstream sabre-io/vobject master up to a95f4e1d (2026-05-31). This is the last upstream commit before PHP 7 support was dropped (sabre-io#767 upstream), and its content matches upstream 4.6.0. Upstream 5.0.0 comes in a separate PR.

The branch has two commits:

1. 2685914e Record upstream master 2024-06-06 as merged. This commit changes no files. Our previous sync (Merge upstream 2024 06 27 #106) was squash-merged, so upstream's history never became part of ours, and every new sync had to redo old conflicts.
   This commit records that sync as a real merge.
2. 82dd5a7f Merge upstream master 2026-05-31. This is the actual sync.

Notable upstream changes

• iTIP: detect STATUS:CANCELLED (fix: check if event status was changed to cancelled and generate appr… sabre-io/vobject#669), send a participation reply on a new event (fix: send participation reply on fresh event sabre-io/vobject#743), handle a null old calendar or event (fix(itip): handle null old calendar/event sabre-io/vobject#753), add an EXDATE when an attendee is removed from a recurring event (Removing attendee from scheduled recurring event should generate an EXDATE property  sabre-io/vobject#728), don't add an EXDATE with a floating timezone (Broker shouldn't add EXDATE property with floating timezone sabre-io/vobject#723)
• Recurrence: use RDATE in time-range checks (fix: use RDATE in time range check and use all instances sabre-io/vobject#735), throw InvalidDataException for an invalid RRULE (Throw InvalidDataException when RRule is invalid sabre-io/vobject#692)
• Parser: better property-name checks and error checks in MimeDir (Improved check on property name sabre-io/vobject#726, Improve error checks in Mimedir parser sabre-io/vobject#727), unknown VALUE data types are allowed (Allow unknown value data types for VALUE sabre-io/vobject#674)
• VTODO: fix alarms relative to DTSTART and PERCENT-COMPLETE validation (Fix Alarm related to DTSTART of VTODO sabre-io/vobject#616, Fix VTODO validation for PERCENT-COMPLETE sabre-io/vobject#664)
• VCard: new getByTypes() method (feat(VCard): add getByTypes method (#717) sabre-io/vobject#718)
• Timezones: deprecated IANA names replaced (fix: Update deprecated timezone names sabre-io/vobject#756), new Exchange timezone name (Add new exchangetimezone 'Amsterdam, Berlin, Bern, Rom, Stockholm, Wien' sabre-io/vobject#618)
• CI: PHP 8.4 and 8.5 added to the matrix, action versions bumped

Conflict resolution

Where our fork deliberately behaves differently, the Proton behaviour is kept:

• Document::createProperty: a malformed or illegal VALUE parameter is still dropped, as in [INBE-269][Fix] drop malformed or illegal VALUE parameter #92. Upstream Allow unknown value data types for VALUE sabre-io/vobject#674 keeps it. Upstream's PropertyTest::testUnknownValuesWillBeIgnored is adapted to match.
• Timezone maps: Greenland stays Atlantic/Stanley ([Calendar] Replace Godthab timezone #65). FLE Standard Time stays Europe/Kiev, matching our Europe/Kyiv → Europe/Kiev redirect in FindFromTimezoneIdentifier. US Eastern Standard Time still resolves to
  America/New_York through extrazones.php. All of upstream's other renames (Kolkata, Yangon, Kathmandu, Buenos_Aires, …) are taken, and upstream's new FindFromTimezoneMapTest is adapted to our values.
• testUnrepairableRRule: upstream Throw InvalidDataException when RRule is invalid sabre-io/vobject#692 is the same change as our throw InvalidDataException when finding invalid RRULE part #109, so upstream's version of the test is taken.
• Version.php stays at 4.34.0. The bump to 4.35.0 comes in the release PR.

Testing

• vendor/bin/phpunit --configuration tests/phpunit.xml: 3279 tests pass, 1 skipped (same skip as on master)
• composer phpstan: no errors
• php-cs-fixer: CI runs it on PHP 7.4. Locally on PHP 8.4 it suggests one trailing comma in a parameter list, which would break PHP 7.4, so it's not applied.

Merging and release

• ⚠️ Merge with "Create a merge commit". Do not squash. Squashing would lose the upstream history again and bring back the old conflicts on the next sync.
• No breaking changes: still php: ^7.4 || ^8.0.
• A follow-up PR release/4.35.0 will bump the version and add the changelog entry.
• After that comes the upstream 5.0.0 sync (PHP 8.2+, typed signatures), which will be our 5.0.0.