Could anyone provide an input here? If this is the expected behaviour then that can be mentioned and the bug report can be closed.

Any update on this issue?

I just ran into this issue too. Sometimes it's possible to work around it by using a key depending on the use case, but that wouldn't work well for the "reset" button example above.

I just ran into this issue too. Sometimes it's possible to work around it by using a key depending on the use case, but that wouldn't work well for the "reset" button example above.

Yeah that is exactly how i worked around this issue although I'd prefer to avoid remounting the component itself tbh as you get the "flashy" effect.

Sorry, I am a bit confused. Could you elaborate on this workaround please?

Use the date you have currently set as a key for the DatePicker itself

I just want to add that setting the key based on the selected value works fine but please don't make the same mistake I made at first.

You should set the key of the calendar via calendarProps and not directly in the root props of the date picker, something like:
<DatePicker {...datePickerProps} calendarProps={{ key: selectedValue?.toString() }} />

This way only the calendar will get re-rendered, which is what we want in this scenario, instead of re-rendering the whole date picker.