2025-7 Release DatePicker breaks implementation in 2025-1

In earlier releases, DatePicker could be used without the selected prop. In our use case, we want customers who are hosting parties to carefully select a delivery date for their perishable food. Now we’re required to provide a default selected date, which can lead to customers accidentally
accepting an incorrect date without proper consideration. The DatePicker component crashes without a selected value.

Additionally, the disabled prop previously accepted day-of-week strings (e.g., “Sunday”). Now, for a 3-month calendar view, we must enumerate every Sunday as individual yyyy-mm-dd date strings, resulting in a significantly larger disabled dates array.

We cannot find any documentation or changelog for these breaking changes. Even if changes are necessary, shouldn’t apps using the 2025-01 API version continue to work until 2026-01, per Shopify’s API versioning policy?

Is there a team responsible for maintaining consistency across UI components? The POS DatePicker doesn’t even support disabled dates, requiring external validation instead of blocking dates at the UI level. Could these components be made more consistent across platforms?

Hi @Jude.Huang

Thanks for sharing this feedback - I’m digging in this on my side now.

Hi again @Jude.Huang

From investigating this it appears the selected prop was previously marked as required in the docs, but it wasn’t enforced until recently. I’ve logged your feedback to the team however.

Thank you Liam. Now we found too many people are taking the default date without thinking. But why this enforcement affects the 2025-01 API? Any chance to add disabled dates to POS UI?