You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Version publishing lag between components to NPM #725
Describe the bug
For several hours after a new version is released, in this case after 0.16.4, NPM will have the core app but not the CLI portion so the dependencies will fail. Not clear if this is due to a CICD pipeline order, NPM processing delay, CICD fail that required an updated push, or something else. I suspect it is part of the pipeline order, and maybe needing to ensure all dependencies are also available before the core is marked as "latest". NOTE: the Error was resolved a few hours after experiencing it, once NPM caught up. The Bug is in reference to the process, to ensure it can be prevented in the future.
To Reproduce
Steps to reproduce the behavior:
Within several hours of a new release
Run: npm install modelcontextprotocol/inspector
Receive error: npm error notarget No matching version found for @modelcontextprotocol/inspector-cli@^0.16.4
Expected behavior
Expect the install to either work, or default to the previous version if not all dependency versions are also available. I think for example the CLI portion needs to be pushed to NPM first and checked for availability, before the core app is also pushed and marked as a stable latest build. For example, when v0.16.3 was released, but not yet marked as latest stable for a few hours after its release, an install would pull v0.16.2, unless I explicitly called for v0.16.3. This delay either intentional or a product of pipeline checks worked as expected. Not sure if something changed, or the delay for v0.16.4 was just not long enough for some background reason.
I don't know how the npm system makes things available, but the entire process runs in a single go, and all the dependencies are published before the inspector itself. I don't know of any way that we can control the rollout of things on the npm side.
Activity
cliffhall commentedon Sep 6, 2025
I don't know how the npm system makes things available, but the entire process runs in a single go, and all the dependencies are published before the inspector itself. I don't know of any way that we can control the rollout of things on the npm side.
Here is the output of the publish-all step for the last release (0.16.5
https://github.com/modelcontextprotocol/inspector/actions/runs/17443177960/job/49531087989
olaservo commentedon Sep 16, 2025
Going to close as not planned since I don't think we have a way to influence this timing.