Lukas Tyla

@laurisvan I would assume that the problem lies in here: https://github.com/mui/mui-x/blob/4e7aaeb828d666d3671f45ab4b336b6c84e4cd40/packages/x-date-pickers/src/AdapterDateFns/AdapterDateFns.ts#L110 Because: ```js console.info(parse('2024-10-11 24:00:00', 'yyyy-MM-dd HH:mm:ss', new Date())); // Invalid Date ``` whereas: ```js console.info(parse('2024-10-11 24:00:00', 'yyyy-MM-dd kk:mm:ss', new...

@nhaebigkerber For now, there has been no progress on this feature, but there clearly is a need for this behavior. 👍 Have you discovered alternative components that support your use...

@JCQuintas I think we agreed to postpone the bump until we find the time to investigate the cause of very significant CI runtime increase. 🤔 https://github.com/mui/mui-x/pull/17216 Have you checked it?...

> I just noticed that the same issue exists when selecting a custom date range e.g. clicking on today's date in the calendar, which makes a "Today" shortcut also unusable,...

Personally, I don't see a need to rush this bump while both vitest and `@mui/internal-test-utils` are still on `v24.x`. 🤔

@flaviendelangle this is happening, because we try to parse `hours` section after the selection of a day in the calendar. In essence, this is an improper format for the `DateTimeRangePicker`,...

> Is this the fixed you just merged ? 😆 Yes, I think that the fix makes sense to avoid complete edge-case failures, but we can discuss if we want...

> All recipe docs in the dedicated Recipes section, or living alongside their main feature docs? I think "Recipes" is mostly relevant to the Data Grid. For other packages we...

Bumping this problem as I have also encountered it when [looking to upgrade](https://github.com/mui/mui-x/pull/17099) `jscodeshift`, which uses `recast`, which uses updated `ast-types`. The diff between the types on `0.14.2` and `0.16.1`...

Blocked by https://github.com/mui/mui-x/pull/17352 due to no longer supporting ESLint