From 6247a7f31acde3750611f313e7edaa4b385054ab Mon Sep 17 00:00:00 2001 From: Jack Date: Sun, 7 Jun 2026 20:19:12 +0800 Subject: [PATCH] =?UTF-8?q?chore:=20spec:rebuild=20script=20(dependency-aw?= =?UTF-8?q?are)=20=E2=80=94=20server-side=20spec-skew=20root-cure?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After changing @objectstack/spec, `pnpm spec:rebuild` rebuilds spec AND every package that depends on it (`turbo run build --filter=...@objectstack/spec`), so the running server's bundled-spec consumers (metadata/rest/runtime/…) reflect the new schema. The skew used to happen because a partial manual rebuild of only packages/spec/dist bypassed turbo's dependency graph, leaving consumers stale. Pairs with objectui clientValidation fix (client never stricter than the live server). Bumps .objectui-sha to that commit. --- .objectui-sha | 2 +- package.json | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.objectui-sha b/.objectui-sha index f501cfa5d..29908ccba 100644 --- a/.objectui-sha +++ b/.objectui-sha @@ -1 +1 @@ -b8b7b16bdcce9b3ac9386c1dd6f1d117816b5dbd +6a7b4989e7a66787e0be2d8b2623d98f3eb0d2d2 diff --git a/package.json b/package.json index 359f9bf47..9a89a8ce9 100644 --- a/package.json +++ b/package.json @@ -9,6 +9,7 @@ "dev:showcase": "pnpm --filter @objectstack/example-showcase dev", "dev:crm": "pnpm --filter @objectstack/example-crm dev", "dev:todo": "pnpm --filter @example/app-todo dev", + "spec:rebuild": "turbo run build --filter=...@objectstack/spec", "test": "turbo run test", "test:e2e": "turbo run test:e2e", "clean": "turbo run clean && rm -rf dist",