@eclipse-glsp/cli 2.8.0-next.6 → 2.8.0-next.8

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
@@ -207,11 +207,11 @@ Publishes all (public) workspace packages of a GLSP repository (replaces `lerna
207
207
  The package manager is auto-detected: pnpm-based repositories publish via `pnpm publish -r`, while
208
208
  not-yet-migrated yarn/lerna-based repositories fall back to the legacy `lerna publish`.
209
209
 
210
- - `next`: applies a canary version (`<root-version>.<commits-since-last-tag>`, e.g. `2.8.0-next.42`) to all
211
- workspace packages and publishes them under the `next` dist-tag. Requires the full git history
212
- (`fetch-depth: 0` in CI) to derive the commit count.
213
- - `latest`: publishes the current package versions under the `latest` dist-tag. Packages whose version
214
- already exists on the registry are skipped.
210
+ - `next`: applies a canary version (`<root-version>.<commits-since-last-tag>`, e.g. `2.8.0-next.42`) to all
211
+ workspace packages and publishes them under the `next` dist-tag. Requires the full git history
212
+ (`fetch-depth: 0` in CI) to derive the commit count.
213
+ - `latest`: publishes the current package versions under the `latest` dist-tag. Packages whose version
214
+ already exists on the registry are skipped.
215
215
 
216
216
  For pnpm repositories publishing is delegated to `pnpm publish -r`, so `workspace:` dependency ranges are
217
217
  rewritten to exact versions; in both cases npm provenance/trusted publishing (`NPM_CONFIG_PROVENANCE`) is