Skip to content

[code-infra] Bump @mui/internal-code-infra to 0.0.4-canary.101 - #119

Closed
Janpot wants to merge 2 commits into
latestfrom
code-infra-publish-npm12-fix
Closed

[code-infra] Bump @mui/internal-code-infra to 0.0.4-canary.101#119
Janpot wants to merge 2 commits into
latestfrom
code-infra-publish-npm12-fix

Conversation

@Janpot

@Janpot Janpot commented Jul 29, 2026

Copy link
Copy Markdown
Member

npm 12 changed npm pkg get version --json to return an object instead of a bare string, so code-infra publish aborted with "No valid version found in root package.json". publish-prepare installs npm@latest, so every publish run now hits it.

Fixed upstream in mui/mui-public#1733, released in 0.0.4-canary.100. This bumps 0.0.4-canary.74 → 0.0.4-canary.101.

Janpot added 2 commits July 29, 2026 10:07
npm 12 changed `npm pkg get version --json` to return an object instead of a
bare string, so `code-infra publish` aborted with "No valid version found in
root package.json". publish-prepare installs npm@latest, so every publish run
now hits it. Fixed upstream in mui/mui-public#1733, released in canary.100.
@cherniavskii

Copy link
Copy Markdown
Member

Does it have any impact in the material-ui-docs repo?
We publish from the material-ui repo, and the latest branch here will be force pushed from material-ui repo anyway.

@Janpot

Janpot commented Jul 29, 2026

Copy link
Copy Markdown
Member Author

no, this is automation that went rogue

@Janpot Janpot closed this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants