Skip to content

Update dependency @pigment-css/react to ^0.0.31 - #826

Open
renovate[bot] wants to merge 1 commit into
devfrom
renovate/pigment-css-react-0.x
Open

renovate[bot] wants to merge 1 commit into
devfrom
renovate/pigment-css-react-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 2, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pigment-css/react (source) ^0.0.29 → ^0.0.31 age adoption passing confidence

Release Notes

mui/pigment-css (@​pigment-css/react)

v0.0.31

Compare Source

May 22, 2026

@pigment-css/react@0.0.31
@pigment-css/nextjs-plugin@0.0.31
@pigment-css/vite-plugin@0.0.31
@pigment-css/unplugin@0.0.31
Docs
Internal

All contributors of this release in alphabetical order: @​ablagoev, @​brijeshb42, @​jooy2, @​oliviertassinari,
@​yoohahn

v0.0.30

Compare Source

Jan 14, 2025

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

@pigment-css/react@0.0.30
@pigment-css/theme@0.0.30
@pigment-css/vite-plugin@0.0.30
Internal

All contributors of this release in alphabetical order: @​bogdanyluk, @​brijeshb42, @​FourwingsY, @​oliviertassinari


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 2, 2026
@renovate

renovate Bot commented Jul 2, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: client/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @mui/material-pigment-css@6.5.0
npm error Found: @pigment-css/react@0.0.31
npm error node_modules/@pigment-css/react
npm error   @pigment-css/react@"^0.0.31" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @pigment-css/react@"^0.0.29" from @mui/material-pigment-css@6.5.0
npm error node_modules/@mui/material-pigment-css
npm error   @mui/material-pigment-css@"^6.5.0" from the root project
npm error   peerOptional @mui/material-pigment-css@"^6.5.0" from @mui/material@6.5.0
npm error   node_modules/@mui/material
npm error     @mui/material@"^6.5.0" from the root project
npm error     1 more (@mui/icons-material)
npm error
npm error Conflicting peer dependency: @pigment-css/react@0.0.29
npm error node_modules/@pigment-css/react
npm error   peer @pigment-css/react@"^0.0.29" from @mui/material-pigment-css@6.5.0
npm error   node_modules/@mui/material-pigment-css
npm error     @mui/material-pigment-css@"^6.5.0" from the root project
npm error     peerOptional @mui/material-pigment-css@"^6.5.0" from @mui/material@6.5.0
npm error     node_modules/@mui/material
npm error       @mui/material@"^6.5.0" from the root project
npm error       1 more (@mui/icons-material)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-30T19_16_25_745Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-30T19_16_25_745Z-debug-0.log

@renovate renovate Bot changed the title chore(deps): update dependency @pigment-css/react to ^0.0.31 Update dependency @pigment-css/react to ^0.0.31 Jul 10, 2026
@renovate
renovate Bot force-pushed the renovate/pigment-css-react-0.x branch from 35a7c74 to bbea799 Compare July 12, 2026 13:17
@renovate
renovate Bot force-pushed the renovate/pigment-css-react-0.x branch 2 times, most recently from 69cc446 to f3ed211 Compare July 24, 2026 14:53
@renovate
renovate Bot force-pushed the renovate/pigment-css-react-0.x branch 2 times, most recently from 4c6bf99 to 6937066 Compare August 13, 2026 04:28
@renovate
renovate Bot force-pushed the renovate/pigment-css-react-0.x branch from 6937066 to 0591053 Compare September 25, 2026 05:01
@coderabbitai

coderabbitai Bot commented Sep 25, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: devsoc-unsw/structs.sh/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 670f626d-9c74-4989-8f80-5514a5b1c204

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants