Dependencies PR created by a bot

https://github.com/mui-org/material-ui/pulls?q=is%3Apr+is%3Aopen+label%3Adependencies

Libraries that need attention

• marked because Core has it as a dependency under docs/packages/markdown. X needs to rely on some code from the Core repo but need to install marked manually because docs is not a package. If the version of the marked in the X repo is different from the Core, it can cause an unknown crash.

Checklist before merging

• CIs are green

• Verson bumped

  • Patch (mostly safe to be merged)
  • Minor (usually safe to be merged)
  • Major (need attention and better have another team member co-review the PR)

• Check the changelog in the Release Notes to see if there is suspicious changes that might affect us.

  

• Check the Passing percentage (should be green)

• Check what are we using the library for (if all the above lists are checked)

  • if it is about infrastructure, mostly safe to be merged. (eg. markdown, prettier, ...etc)
    • Example, aws-sdk has minor bumped but all the changes aren’t related to Dynamo client (the only API we use from this package), so it is quite safe to be merged.
  • if it is the package dependency, eg. popper-core, need another team member to co-review the PR and tested the related component.

• Before merging, try to add comment anything that you think it is worth documenting (in case something wrong)