Skip to content

[internal] Prepare for v5 stable release#28240

Merged
mnajdova merged 4 commits intomui:nextfrom
mnajdova:prepare/stable-release
Sep 10, 2021
Merged

[internal] Prepare for v5 stable release#28240
mnajdova merged 4 commits intomui:nextfrom
mnajdova:prepare/stable-release

Conversation

@mnajdova
Copy link
Member

@mnajdova mnajdova commented Sep 9, 2021 •
edited
Loading

List of changes:

  • Handle all #default-branch-switch comments
  • Replace next.material-ui.com with material-ui.com
  • Replace the @mui/@next with @mui/
  • Add redirects from next.material-ui.com -> material-ui.com
  • Change the tag from next to latest

@mnajdova mnajdova marked this pull request as draft September 9, 2021 11:52
@mui-pr-bot
Copy link

mui-pr-bot commented Sep 9, 2021 •
edited
Loading

No bundle size changes (experimental)

Generated by 🚫 dangerJS against 7f07f1f

@github-actions github-actions bot mentioned this pull request Sep 9, 2021
Closed
@mnajdova mnajdova marked this pull request as ready for review September 9, 2021 13:08
@eps1lon
Copy link
Member

eps1lon commented Sep 10, 2021

Shouldn't this happen after we've switched to master?

siriwatknp
siriwatknp approved these changes Sep 10, 2021
View reviewed changes
Copy link
Member

@siriwatknp siriwatknp left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

waiting for response about @eps1lon question.

@mnajdova
Copy link
Member Author

mnajdova commented Sep 10, 2021

Shouldn't this happen after we've switched to master?

We anyway won't release the documentation until we have the stable release, so I don't think it matters if we merge this earlier. It's just a matter of a few days now, we just need to make sure we finish the checklist by Wednesday.

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged. label Sep 10, 2021
@eps1lon
Copy link
Member

eps1lon commented Sep 10, 2021

So the plan is to not release another release candidate?

@mnajdova
Copy link
Member Author

mnajdova commented Sep 10, 2021

So the plan is to not release another release candidate?

We did a release this Wednesday (two days ago). The stable release is planned for next Wednesday.

@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged. label Sep 10, 2021
eps1lon
eps1lon approved these changes Sep 10, 2021
View reviewed changes
Copy link
Member

@eps1lon eps1lon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the plan is to not release another release candidate?

We did a release this Wednesday (two days ago). The stable release is planned for next Wednesday.

I take this as a yes. Then we can merge this.

@mnajdova mnajdova merged commit 575b953 into mui:next Sep 10, 2021
@zannager zannager added the internal Behind-the-scenes enhancement. Formerly called “core”. label Jan 26, 2023
@oliviertassinari oliviertassinari changed the title [core] Prepare for v5 stable release [internal] Prepare for v5 stable release Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@eps1lon eps1lon eps1lon approved these changes

@siriwatknp siriwatknp siriwatknp approved these changes

Assignees

No one assigned

Labels

internal Behind-the-scenes enhancement. Formerly called “core”.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@mnajdova @mui-pr-bot @eps1lon @siriwatknp @zannager