clavue 8.28.18 → 8.28.20

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
@@ -1,4 +1,4 @@
1
- # Clavue v8.28.18
1
+ # Clavue v8.28.20
2
2
 
3
3
  ![Clavue cover](https://unpkg.com/clavue/image.png)
4
4
 
@@ -65,8 +65,8 @@ npx -y clavue
65
65
  Run a specific version with `npx`:
66
66
 
67
67
  ```bash
68
- npx -y clavue@8.28.18 --version
69
- npx -y clavue@8.28.18
68
+ npx -y clavue@8.28.20 --version
69
+ npx -y clavue@8.28.20
70
70
  ```
71
71
 
72
72
  Install globally from npm when you want the `clavue` command to stay available:
@@ -86,7 +86,7 @@ curl -fsSL https://unpkg.com/clavue/install.sh | bash
86
86
  Install a specific version globally:
87
87
 
88
88
  ```bash
89
- curl -fsSL https://unpkg.com/clavue@8.28.18/install.sh | bash -s -- 8.28.18
89
+ curl -fsSL https://unpkg.com/clavue@8.28.20/install.sh | bash -s -- 8.28.20
90
90
  ```
91
91
 
92
92
  ### Troubleshooting: `ENOTEMPTY` / `bash: clavue: No such file or directory`
@@ -325,7 +325,8 @@ Companion commands are still available and can either follow the current app pro
325
325
  - Public install entrypoint: `npx -y clavue`
326
326
  - `src/` is the development surface for new changes, while the checked-in `dist/` bundle is the current shipped runtime artifact
327
327
  - `types/generated/` holds generated contract types that stay outside authored runtime source
328
- - GitHub Releases publish installable archives plus `install.sh`
328
+ - npm is the only package publishing target; GitHub Releases are not part of the normal release path
329
+ - Official website release updates are generated locally as changelog blocks and version usage notes before any site edit or deploy
329
330
  - npm distributes the same tracked top-level runtime entrypoints that power `dist/cli.js`, without shipping nested `dist/` development artifacts, `.map` files, or `.d.ts` files
330
331
  - `npm run verify:source-build` rebuilds the CLI from `src/` into `experimental-dist/` and smoke-tests the Node entrypoints as a structural guard
331
332
  - `dist/` is still the shipped artifact today, but release verification now requires both tracked `dist/` integrity and a bootable source rebuild