lensmcp 1.23.9 → 1.23.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -84,7 +84,7 @@ scope of the existing install.
84
84
  ### `lensmcp upgrade`
85
85
 
86
86
  ```bash
87
- lensmcp upgrade [version] [--dry-run] [--no-install] [--no-plugins] [--no-global] [--no-restart]
87
+ lensmcp upgrade [version] [--dry-run] [--no-install] [--no-plugins] [--no-global] [--no-restart] [--no-registry-check]
88
88
  ```
89
89
 
90
90
  One command that moves the whole machine to one lensmcp version (latest by default), in
@@ -102,8 +102,14 @@ the only order that works:
102
102
  when no package.json moved, if it provably lags the target.
103
103
 
104
104
  Per-workspace failure posture: one failed install never blocks the others, every failure
105
- names the command that finishes the job by hand, and re-running converges. `--dry-run`
106
- prints the full plan without changing anything.
105
+ names the command that finishes the job by hand, and re-running converges — a workspace
106
+ whose package.json is already at the target but whose node_modules is not gets its install
107
+ run again. `--dry-run` prints the full plan without changing anything.
108
+
109
+ A version the npm registry does not have is refused before anything is touched (a typo, or a
110
+ publish still in flight); `--no-registry-check` skips the question. The command ends by naming
111
+ each workspace that still needs `lensmcp setup`: the lens gates its tools until setup has run
112
+ for the installed version, so every upgrade closes that gate.
107
113
 
108
114
  ### `lensmcp doctor`
109
115