What material-ui version are you using?

[Domino987]

We wanted to get a rough overview of which material-ui version is used the most.

For that, we wanted to create a poll to see what needs to be supported the most.

Please reply with an emote:

🎉 Material ui v5 > beta.0
👍 Material ui v4 > 4.12.x
❤️ Material ui v4 < 4.11.x

[iamchathu]

We upgraded to @mui/material the version 5

[LuchoTurtle]

@Domino987 This relates to quite the interesting scenario I'm in. The PRs that are being merged into master, I assume they're not being merged also in the next branch (the one that has MUI 5), right? I'm asking this because I'm in the middle of migrating from MUI v4 to v5 and it'd be amazing if new PRs (such as #343 ) would also be available on this next branch so new material-table-core features wouldn't get lost by migrating from v4 to v5.

Is this possible or what can we do to fix this? 🤔

[Domino987]

Hi
Yes the changes from master are regularly merged into next so nothing is lost.
And we do regular release of both branches.

[LuchoTurtle]

Hi
Yes the changes from master are regularly merged into next so nothing is lost.
And we do regular release of both branches.

Proper stuff, awesome! Without wanting to nag, do we have an ETA for the next release on the next branch? 👀

[Domino987]

I just did 😃

[LuchoTurtle]

@Domino987 It's unfair how good you are, mate haha! Cheers, thank you so much!

[b3ni]

When is the next tag updated with the latest changes?

[Domino987]

I try to do that at regular intervals but I am still waiting for one PR to be merged.

Update:
I just released a new version for both.

[Gzbox]

We upgraded to @mui/material the version 5

[bhkangw]

Hi we are using MUI v5! Any idea when the prerelease version will be finished testing and officially released?

[Domino987]

It is always on par with the master version so you can expect the same code for each branch. Since about half of the downloads are still for v4, maybe we wait a bit more. But again, it's the same code just adjusted for now.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You can reopen it if it required.