@vegastack/design 0.9.2 → 0.9.5

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vegastack/design",
3
- "version": "0.9.2",
3
+ "version": "0.9.5",
4
4
  "description": "VegaStack design system — cn utility, icon runtime, Tailwind v4 preset, and the vegastack-design CLI (tokens ship separately as @vegastack/design-tokens)",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -181,8 +181,9 @@ Copy-in means no automatic updates.
181
181
  pnpm exec vegastack-design check-updates # ⬆ update · ≈ drift · ✓ up to date
182
182
  ```
183
183
 
184
- Then per stale component: `shadcn add @vegastack/<name> --diff` to review, `--overwrite` to apply,
185
- and re-run the step-3 post-write verification. Details and CI wiring:
184
+ Then per stale component: `pnpm exec shadcn add @vegastack/<name> --diff` to review, and apply it with
185
+ the full step 1 → 3 flow again (a fresh pre-write `verify --save`, the `--overwrite` copy-in, the
186
+ post-write verification against that new payload). An old saved payload no longer matches. Details and CI wiring:
186
187
  [references/registry-integrity.md](references/registry-integrity.md).
187
188
 
188
189
  Add the Renovate preset `github>VegaStack/renovate-config` so additive token bumps arrive as PRs.
@@ -56,7 +56,7 @@ just drift in the copied files.
56
56
  ## Step 2 — copy-in
57
57
 
58
58
  ```bash
59
- pnpm dlx shadcn@latest add @vegastack/button
59
+ pnpm exec shadcn add @vegastack/button
60
60
  ```
61
61
 
62
62
  The registry item content carries a provenance header (`// @vegastack <name>@<ver> sha256-…`), but
@@ -125,8 +125,8 @@ real leading-comment and configured-alias transforms.
125
125
  edits. It refuses to attach credentials to any origin other than `VEGASTACK_TRUSTED_REGISTRY_ORIGIN`
126
126
  (default `https://design.vegastack.com`) and never follows registry redirects.
127
127
 
128
- Per stale component: `shadcn add @vegastack/<name> --diff` to review, then `--overwrite` to apply,
129
- then re-run the post-write verification above.
128
+ Per stale component: `pnpm exec shadcn add @vegastack/<name> --diff` to review, then repeat the full
129
+ flow with a fresh payload: pre-write `verify --save`, `--overwrite`, post-write verification.
130
130
 
131
131
  Status is computed by hash, so a component correctly reads `up to date` when the registry's global
132
132
  version bumped but that component's content did not change.