[DataGridPremium] Update exceljs fork (@cherniavskii)#22668
Merged
Conversation
github-actions
Bot
requested review from
MBilalShafi,
cherniavskii and
michelengelen
June 2, 2026 14:38
cherniavskii
force-pushed
the
cherry-pick-22658-to-v8.x
branch
from
June 2, 2026 15:06
a87e943 to
ceb006d
Compare
|
Deploy preview: https://deploy-preview-22668--material-ui-x.netlify.app/ Bundle size report
|
cherniavskii
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #22658
Changelog
This release includes a version bump of the
@mui/x-internal-exceljs-forkpackage to address the vulnerable dependencies.The following CVEs are fixed:
To make this security update possible, we bumped the
nodeversion requirement from>=14.0.0to>=14.17.0.Node.js 14.17.0 was released in May 2021, so we consider it safe to bump the requirement without causing issues for our users.