Packages

@mui/material-pigment-css

9.5.0 · 9 Oct 2026MIT17.3k / weekRepositoryHomepagenpmAtom feed

Your version

7.3.3

1 Oct 2025Where it was published

7.3.11 is the newest release of 7.x.

In short

1 removed6 fixed24 changed6 internal

  • Removed

    Remove copy-files command usage from packages

Release note

The section about @mui/material-pigment-css of a note shared by several packages.

A big thanks to the 14 contributors who made this release possible.

Core

  • Fix year in Punta Cana retreat post

  • Punta Cana retreat post

  • Publish from CI

  • Convert reportBrokenLink script to ts

  • Update module resolution for typescript@next

  • Run continuous releases during ci-check

  • Fix github actions check for continuous release

  • Address high/critical dependabot reports

  • Update ci.yml triggers

  • Exact match for renovate file name

  • Disable dependency update for @material-ui/core in codemod

  • Transpile assertion-error in karma tests

  • Disable browserstack on circleci cron jobs

  • Removed

    Remove copy-files command usage from packages

  • Low-hanging ts conversion

  • Bring batch of changes from vitest PR

  • Remove dependency on fs-extra

  • Make error code extraction independent of build

  • Fix markdown generation script to find correct files

  • Fix unnecessary redirects

  • Remove dangerouslySetInnerHTML for ad description

  • Display "View as Markdown" only on Material UI

  • Fix JSON files not being imported in TS demos

  • Turn literal | (string & {}) to PropTypes.string

  • Bump node.js version and make local usage strict

  • Remove "main" fields from publishable packages

  • Refactor useForkRef TS types: tighten cleanupRef and simplify ref typing

  • Fix naming to match convention

  • Fix naming to match convention

  • Use same option as other repositories

  • Normalize <meta name='viewport'

  • Normalize charset='utf-8'

All contributors of this release in alphabetical order: @alelthomas, @bernardobelchior, @brijeshb42, @christopherschroer, @Janpot, @Jayesh-11, @jonyen, @mapache-salvaje, @monam2, @oliviertassinari, @sai6855, @siriwatknp, @wo-o29, @ZeeshanTamboli

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.