create-apollo-suite-monorepo 1.0.1433 → 1.0.1435

package/README.md

@@ -152,6 +152,21 @@ Without the mirror the drizzle-kit patch never applies, and every
 constraint and prompts to truncate any non-empty table that owns one —
 in CI (no TTY) the push aborts.
 
+It also writes the backend's own `next`, `react` and `react-dom` specifiers
+into the root `overrides`, so every workspace package — your frontend and
+every `apps/cms-plugins/*` suite app included — resolves the same copy the
+backend does, and the next `pnpm backend:update` moves them for you. Suite
+apps are bundled into the backend's Next build; a second `next` (or React)
+makes pnpm install a second `next-safe-action`, and typecheck fails with
+TS2345 across every `useAction` call (apollo-suite #1915, #1916). The cost is
+that your frontend follows the backend's `next`/`react` too.
+
+One-time step for an existing consumer, after the first `backend:update` that
+brings this in: commit the rewritten root `pnpm-workspace.yaml` and
+`pnpm-lock.yaml`, and check `pnpm why next-safe-action` shows ONE copy.
+Adding `node apps/backend/scripts/sync-root-workspace.mjs --check` to CI makes
+a submodule bump that skipped `backend:update` fail loudly instead.
+
 ### Scaffolds created before `sync-root-workspace`
 
 Run it once by hand, then reinstall:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-apollo-suite-monorepo",
-  "version": "1.0.1433",
+  "version": "1.0.1435",
   "description": "Scaffold a monorepo with a frontend app and Apollo CMS as a git submodule backend (single-origin via Next.js rewrites + assetPrefix)",
   "bin": {
     "create-apollo-suite-monorepo": "index.mjs"