Describe the bug
Over here, one can see, that enabled array being formed by starting from rangeStart and advancing one day each time until rangeEnd reached.
If rangeStart started before clock switching one hour backwards for daylight time saving in winter (in 2025 it was 26 of October), then cycle will start from date one hour ahead (e.g. Tue Oct 21 2025 03:00:00 GMT+0300 (Eastern European Summer Time)), advance one day exactly and it will reach rangeEnd date in a state, where clock switching didn't happen (for 4th of November, currentDate would be equal to Tue Nov 04 2025 02:00:00 GMT+0300 (Eastern European Standard Time)). But new Date(rangeEnd) is capable of handling clock switch, so it will return correct result (e.g. Tue Nov 04 2025 02:00:00 GMT+0200 (Eastern European Standard Time)), which will be smaller number compared to current Date (condition here) and will leave last day excluded from enabled array.

To Reproduce
Steps to reproduce the behavior:

1. Provide enabledDates range starting before 26th of October and ending after 26th of October 2025
2. Open Datepicker
3. Check disabled dates in calendar, last day of enabledDates range will be disabled

Expected behavior
All dates from enabledDates range (including start and end date) will not be disabled in Datepicker calendar

Desktop (please complete the following information):

• OS: MacOS 26
• Browser: Chrome
• Version: 141