[release] v5.14.9

[DiegoAndai]

PR for the release of version 5.14.9

[mui-bot]

Netlify deploy preview

https://deploy-preview-38920--material-ui.netlify.app/

@material-ui/core: parsed: +Infinity% , gzip: +Infinity%
@material-ui/lab: parsed: +Infinity% , gzip: +Infinity%
@material-ui/styles: parsed: +Infinity% , gzip: +Infinity%
@material-ui/private-theming: parsed: +Infinity% , gzip: +Infinity%
@material-ui/system: parsed: +Infinity% , gzip: +Infinity%
@material-ui/unstyled: parsed: +Infinity% , gzip: +Infinity%
@material-ui/utils: parsed: +Infinity% , gzip: +Infinity%
@mui/material-next: parsed: +Infinity% , gzip: +Infinity%
@mui/joy: parsed: +Infinity% , gzip: +Infinity%

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against 0e84cb6

[oliviertassinari]

A link to the docs could be great. Or maybe even an image/video preview. We are not selling it 😁

[DiegoAndai]

Added link to the docs
@siriwatknp @zanivan, let me know if you have an image or video you wish to add 😊

[michaldudak]

I don't agree here about images or video clips. We can brag about new features on social media, but the changelog should be concise and highlight changes from the previous version. It's not a means of marketing.

A link is fine, though.

[siriwatknp]

Yep, a link is enough for the changelog.

[oliviertassinari]

I don't agree here about images or video clips. We can brag about new features on social media, but the changelog should be concise and highlight changes from the previous version. It's not a means of marketing.

@michaldudak There are different schools on this.

1. Changelog first: https://github.com/prisma/prisma/releases, https://github.com/drizzle-team/drizzle-orm/releases,
2. Twitter first: https://github.com/chakra-ui/chakra-ui/releases https://github.com/shadcn-ui/ui/releases
3. Blog posts first: https://github.com/microsoft/TypeScript/releases, https://nextjs.org/blog, https://v5.mantine.dev/changelog/5-8-0/
4. Doesn't announce

I feel the problem in our case is that we fall most often under "Doesn't announce" 😁. I would be much in favor of 3.

[sai6855]

@DiegoAndai these PRs can be merged #38876 #38814 and maybe #38753 could also go

[siriwatknp]

Off-topic: not sure why the system has them as dev dependencies 🤔

[mnajdova]

The dependencies are now explicit, we use them in the tests.

[oliviertassinari]

I would challenge that having this here is a net-positive, I don't understand how #38859 (comment).

[siriwatknp]

The versions look good to me, just a few open questions.

[DiegoAndai]

I think I discovered the cause of the yarn.lock unexpected update:

In #38859, the MUI packages were added explicitly to the root package.json.

Running yarn release:version didn't update these versions in the root package.json (file here). There's an existing issue about it. This is what caused the yarn.lock update, which is not correct.

@michaldudak, how might we proceed here?

cc: @ZeeshanTamboli @siriwatknp

[michaldudak]

Sorry for causing trouble. I'm attempting a fix in #38940.