Events all show up at 1am of the correct day if a VTIMEZONE block contains info for daylight saving dates for more than 2 years

[TobiasGasser]

Background:
We use the spatie/icalendar-generator package to create the ics file. It automatically creates a (correct) VTIMEZONE block containing info about the daylight saving dates and the standard dates.
If the calendar only contains events of this year (e.g. 2025) the VTIMEZONE block will contain daylight saving info as follows:

BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
DTSTART:20250330T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE

If there are events present in 2026 as well it will have more such daylight saving info present as follows:

BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
DTSTART:20250330T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261025T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20270328T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE

The problem
In the second case with more such daylight saving blocks all events are created in the android calendar to start at 1am.

This behaviour can be reproduced in a calendar with 2 events: one in 2025, another in 2026. Removing the one in 2026 will let the times be imported correctly. Having it in will cause the erroneous times.

Here is a link to the ics test-feed with the two dates present: https://band.zone/cal/2d6ccb9a-6782-411b-80fa-ea9f3e510805

Other calendars (directly adding the same URL to Google, Apple, eMClient) will show the events correctly.
The icalendar validator also detects no error in the feed.

Question
Is this a known/intended limitation or may it be a bug?

THX a lot!
Tobi

(I am using the paid icsx5 in version 2.4.2)

[TobiasGasser]

Moved info to #419