Lukas Tyla

> And also resolved the first comment 🙌 Nitpick: You have removed the comment from where it made sense, as that job calls `release:changelog`. 🙈

Could someone restart the failed GH Action? Looks like a flaky error. 🤔

Sorry for the delayed answer @ManuC84. @michelengelen thank you for a detailed response. As you mentioned, the current API has no clear way to achieve the desired result. The `TimePicker`...

Adding "on hold" label. `@mui/internal-test-utils` needs to first bump the `vitest` version and adjust the code.

@vrama628 [Here is](https://stackblitz.com/edit/react-wjvuys-rrvejz?file=Demo.tsx) an updated StackBlitz example with needed fixes to avoid the incorrect `any` resolution. The problem was mainly with the mix of `Date` and `Dayjs` types. 😉 Does...

> the problem is that TS did not complain in his example 😬 Oh, gotcha. 👍 Sorry for missing the point. 🙈 Regardless, TS reports a problem with the provided...

> As I understand it, the codesandbox is here to demonstrate that `PickerValidDate` is `any`| instead of `Dayjs`. Did you mean `never`, instead of `Dayjs`? 🤔 💡 This is a...

> 🤔 in his example he has `any`, he should have `Dayjs` since he imports `AdapterDayjs` > And locally I have `Dayjs`, not sure how you ended up with `never`...

> A solution could be to replace relative links from `v5.mui.com` to X docs by absolute links to `v7.mui.com/x/` the latest compatible version. Such that we remove 404. And if...

> It would be nice to have an option to change the behavior of this button to show the months view instead of the years view Could you clarify your...