uptide 0.7.3 → 0.7.4-next.20261012000301
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 +5 -1
- package/dist/{chunk-3677J24F.js → chunk-57W2CR2P.js} +8 -8
- package/dist/{chunk-R5AVTJOT.js → chunk-CJN2BH6Q.js} +6 -6
- package/dist/{chunk-K3IY7WMD.js → chunk-PYEKNRTZ.js} +1 -1
- package/dist/{chunk-G5YPY7VA.js → chunk-T6SC2JX2.js} +1 -1
- package/dist/engine-worker.js +1 -1
- package/dist/index.js +3 -3
- package/dist/{publish-T2VGNGRW-GTCSYEJM.js → publish-MAKY5LPJ-LRRVT6H6.js} +1 -1
- package/dist/worker.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -24,7 +24,11 @@ npx uptide pr --branch uptide/zod-4.6.5 # prints the plan; add --yes to push
|
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
`npx uptide` with no command shows where zod and stripe stand: installed, latest, majors
|
|
27
|
-
behind.
|
|
27
|
+
behind. `fix` preserves workspace and companion ranges that already accept the target,
|
|
28
|
+
reports them as **already compatible**, and widens rejecting peer ranges without dropping
|
|
29
|
+
existing alternatives. The lockfile and installed target and companions must still match
|
|
30
|
+
the exact planned versions; `fix` and `verify` fail if installed versions differ.
|
|
31
|
+
Everything else: [getting started](docs/getting-started.md).
|
|
28
32
|
|
|
29
33
|
## Why Uptide
|
|
30
34
|
|