- Shipped
- September 7, 2026 at 2:01 AM UTC
- Author
- Kamo
- Commit
- ac6c59f
updateEvent restated the title, description, location, colour, timezone and deep link, and dropped meetingUrl — so a link added to a callback that had already been booked was accepted by the API and silently discarded. createForMember has always written the field, which made this look like it worked on the way in and fail only on an edit. meetingSignature did not count the link either, so even once it was applied the SEQUENCE stayed put. That is the worse half: every guest holds an invitation to the old room, and an update arriving at a sequence they already hold is ignored by every iCalendar client — they would sit in the old room while the meeting happened in the new one, and nothing would ever tell them. **************** has counted meetingUrl since it was written; this is the service-to-service path catching up with it.