[release] v6.2.0

[mj12albert]

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Netlify deploy preview

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

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against 91eda83

[EfstathiadisD]

Quick question. I might have missed it but can we make sure Joy UI will be compatible with React19 as well?

I understand it's not Prio 1 but it is used and I think a release is warranted here!

[DiegoAndai]

MUI X also needs a Joy release to unblock mui/mui-x#15769 (comment).

The types are already updated, I think we only need to release, may I ask you to include it here @mj12albert?

cc: @aarongarciah @mnajdova

[mj12albert]

I've bumped the Joy version as well!

[mj12albert]

Waiting for #44709 as well CC @mnajdova

[DiegoAndai]

Latest published version of joy is 5.0.0-beta.48 (released from the v5.x branch), so we should bump it to 49.

@aarongarciah @siriwatknp do you recall if there might be any issues releasing joy from this branch?

I think it should be fine, as no breaking changes to Joy should've been made since the v6 master/next split. I would prefer to release them from this branch as it's ready with React 19 changes, whereas v5.x is still missing some final changes.

[DiegoAndai]

We'll also need a base release 😅 @mj12albert

[aarongarciah]

I can't recall any issues.

[mnajdova]

Waiting for #44709 as well CC @mnajdova

Merged, thanks!

[rodrigogs]

It's not possible to install 6.2.0 because core-downloads-tracker@6.2.0 doesn't exist yet.

npm install @mui/material@latest @emotion/react@latest @emotion/styled@latest
npm error code ETARGET
npm error notarget No matching version found for @mui/core-downloads-tracker@^6.2.0.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /Users/rodrigo.gomes/.npm/_logs/2024-12-11T03_51_34_556Z-debug-0.log

Maybe it wasn't deployed?

[mj12albert]

@rodrigogs It should be fixed now (#44724 (comment)), please try again 🙏

[rodrigogs]

It worked, thank you!