Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v7.23.4 #16003

Merged
merged 4 commits into from
Dec 27, 2024
Merged

v7.23.4 #16003

merged 4 commits into from
Dec 27, 2024

Conversation

DanailH
Copy link
Member

@DanailH DanailH commented Dec 26, 2024

No description provided.

@DanailH DanailH added the release We are shipping :D label Dec 26, 2024
@DanailH DanailH self-assigned this Dec 26, 2024
@mui-bot
Copy link

mui-bot commented Dec 26, 2024

Deploy preview: https://deploy-preview-16003--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 8ccaf79

@DanailH DanailH requested a review from a team December 26, 2024 13:43
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@@ -201,9 +201,9 @@
"react-is": "^18.3.1",
"@types/node": "^20.16.11"
},
"packageManager": "pnpm@9.12.1",
"packageManager": "pnpm@9.15.1",
Copy link
Member

Choose a reason for hiding this comment

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

Do you know what caused this change?

Copy link
Member Author

@DanailH DanailH Dec 26, 2024

Choose a reason for hiding this comment

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

I did 😄 It's 9.15.1 on master and I figured they should match, right?

Copy link
Member

Choose a reason for hiding this comment

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

Hmm, I'm not sure 🤔
Maybe someone from @mui/code-infra can advise?

Copy link
Member

Choose a reason for hiding this comment

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

I have no arguments against this. 🤷
It goes out of sync because we stop bumping dependencies on anything other than master. 🤷

Copy link
Member Author

Choose a reason for hiding this comment

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

@LukasTy I did it mostly for convenience - It's annoying to switch the version of pnpm when releasing from master and v7.x
On another note - have you thought about stopping the releases for v7?

Copy link
Member

Choose a reason for hiding this comment

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

I did it mostly for convenience - It's annoying to switch the version of pnpm when releasing from master and v7.x

Are you using corepack?
The version should be picked up automatically if you have it installed.
But I agree that it could still end up annoying if the person doing the release does not have that particular outdated version released. 🙈

On another note - have you thought about stopping the releases for v7?

I don't think we've had this discussion yet. 🤔
AFAIK, we keep releasing the current stable if there are any relevant bug fixes and/or localization changes while we are in the pre-release phase.
Once the current major changes—releasing prior versions becomes increasingly less frequent. It's mostly bigger bug fixes that we consider back-porting.

DanailH and others added 2 commits December 26, 2024 21:41
Co-authored-by: Michel Engelen <[email protected]>
Signed-off-by: Danail Hadjiatanasov <[email protected]>
Co-authored-by: Andrew Cherniavskii <[email protected]>
Signed-off-by: Danail Hadjiatanasov <[email protected]>
@@ -201,9 +201,9 @@
"react-is": "^18.3.1",
"@types/node": "^20.16.11"
},
"packageManager": "pnpm@9.12.1",
"packageManager": "pnpm@9.15.1",
Copy link
Member

Choose a reason for hiding this comment

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

I have no arguments against this. 🤷
It goes out of sync because we stop bumping dependencies on anything other than master. 🤷

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Lukas Tyla <[email protected]>
Signed-off-by: Danail Hadjiatanasov <[email protected]>
@DanailH DanailH merged commit f13dd69 into mui:v7.x Dec 27, 2024
16 checks passed
Copy link
Member

Choose a reason for hiding this comment

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

Hmm, something went wrong with this release. The @mui/x-internals package wasn't bumped for some reason, which results in the following error: https://stackblitz.com/edit/react-fur42je2?file=Demo.tsx

Error in turbo_modules/@mui/[email protected]/node/components/GridColumnHeaders.js
The entrypoint for '@mui/x-internals' could not successfully be resolved. The file '/turbo_modules/@mui/[email protected]/forwardRef' does not exist. Please log an issue with the package author or check for an updated version of the package.

And indeed, there's no forwardRef export in @mui/[email protected] that the latest version is trying to use: https://unpkg.com/@mui/[email protected]/package.json

@DanailH We need to release a bugfix that would include releasing @mui/x-internals

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, we are on top of it. @MBilalShafi is prepping a patch because only releasing x-internals won't fix the issue.

@cherniavskii cherniavskii mentioned this pull request Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release We are shipping :D
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants