@mui/material 6.2.0 download broken because of non-existing reference to @mui/core-downloads-tracker@^6.2.0

[Tasin5541]

Steps to reproduce

Steps:

1. Upgrade @mui/material version to 6.2.0 in package.json
2. Run npm i

Current behavior

Trying to upgrade to version 6.2.0 results in the following error:

@mui/core-downloads-tracker: No matching version found for @mui/core-downloads-tracker@^6.2.0

Expected behavior

No response

Context

No response

Your environment

npx @mui/envinfo

    System:
    OS: Windows 11 10.0.26100
  Binaries:
    Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (131.0.2903.63)
  npmPackages:
    @emotion/react: ^11.14.0 => 11.13.5
    @emotion/styled: ^11.14.0 => 11.13.5
    @mui/core-downloads-tracker:  6.1.10
    @mui/icons-material: ^6.2.0 => 6.1.10
    @mui/material: ^6.2.0 => 6.1.10
    @mui/private-theming:  6.1.10
    @mui/styled-engine:  6.1.10
    @mui/system:  6.1.10
    @mui/types:  7.2.19
    @mui/utils:  6.1.10
    @mui/x-date-pickers: ^7.23.1 => 7.23.1
    @mui/x-internals:  7.23.0
    @types/react: ^18.3.16 => 18.3.14
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.7.2 => 5.7.2

Search keywords: No matching version, @mui/core-downloads-tracker

[MasterProvider]

same here

[khajornsakworking]

same here

[mj12albert]

Seems the script didn't publish some packages, I don't know if it's related but I had some network issues at the time

I'm fixing this now

[mj12albert]

It's republished https://www.npmjs.com/package/@mui/core-downloads-tracker/v/6.2.0

I've tested an installation of 6.2 in a sandbox: https://codesandbox.io/p/sandbox/material-ui-v6-2-9g8j56?file=%2Fpackage.json%3A13%2C5-14%2C26

[Tasin5541]

It's republished https://www.npmjs.com/package/@mui/core-downloads-tracker/v/6.2.0

I've tested an installation of 6.2 in a sandbox: https://codesandbox.io/p/sandbox/material-ui-v6-2-9g8j56?file=%2Fpackage.json%3A13%2C5-14%2C26

Can confirm, it's wokring now.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@Tasin5541 How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

[alexanderbird]

Should there be a change to the publish process to prevent this from happening again? It looks like it happened with 5.10.6 also (#34394). I would have thought that if @mui/core-downloads-tracker isn't published, that the publish process would stop. Instead, it seems like the process continued despite @mui/core-downloads-tracker not being published. Will this happen again in future deployments?