@umriss-ui/schedule 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -15,6 +15,22 @@ moves from here under the rule above.
 
 ---
 
+## 0.7.1 – Core 0.33.0, charts 0.16.0 (Oct. 2026)
+
+Needs `@umriss-ui/core` 0.33 and `@umriss-ui/charts` 0.16; the peer ranges move to `^0.33.0` and `^0.16.0`.
+
+### Added
+
+- **The unit tests run against React 18.3.1 and 19 in CI**, and a schedule is rendered to a string with no `window` in a test (`tests-unit/ssr.test.tsx`): its labelled frame and empty canvases.
+
+### Changed
+
+- **Every entry begins with `"use client";`.** The built file `dist/schedule.js` starts with the directive, then the stylesheet import, so a bundler that splits server from client code takes each as client code. The directive is written to the built entries only; the sources are unchanged.
+
+- **Every export is a client component.** A hook called in a Server Component now fails with React's message about a client reference, not one about `useState`.
+
+---
+
 ## 0.7.0 – The summary counts the milestones (Oct. 2026)
 
 Needs `@umriss-ui/core` 0.32; the peer range moves to `^0.32.0`.

package/README.md

@@ -19,7 +19,14 @@ Both `@umriss-ui/core` and `@umriss-ui/charts` are **peer dependencies**
 (ADR-0022): the schedule takes its styling regime, provider, formats and
 wording from core, and its time arithmetic — the affine scale, the time steps,
 the working calendar, the canvas colour resolution — from charts. React 18 or
-19 as a peer as well.
+19 as a peer as well; the unit tests run against 18.3 and 19 in CI.
+
+Every entry begins with `"use client"`, the directive a framework
+with Server Components reads to treat a module as client code. No test runs
+inside such a framework: the
+schedule is rendered to a string in a test. On a server it gives its labelled
+frame and empty canvases; the lanes, subtasks and the summary's counts arrive
+on the client after mount.
 
 ## The smallest schedule that runs
 
@@ -161,7 +168,8 @@ label and time.
 ## Not yet
 
 What the schedule does not do today, and waits for a caller who needs it (what
-it never does stands in ADR-0032):
+it never does stands in ADR-0032): umriss shows the reader's time, and a
+plant's zone is not yet offered (ADR-0060).
 
 * **Stacked overlap** — overlapping subtasks packed into sub-lanes on request;
   today an overlap is always drawn offset, as the finding it is.

package/dist/schedule.js

@@ -1,3 +1,4 @@
+"use client";
 import "./schedule.css";
 var hn = Object.defineProperty;
 var cn = (s, t, e) => t in s ? hn(s, t, { enumerable: !0, configurable: !0, writable: !0, value: e }) : s[t] = e;

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.7.0
+# @umriss-ui/schedule 0.7.1
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
   "license": "MIT",
   "author": "Roman Händler",
@@ -50,8 +50,8 @@
   "peerDependencies": {
     "react": ">=18",
     "react-dom": ">=18",
-    "@umriss-ui/charts": "^0.15.0",
-    "@umriss-ui/core": "^0.32.0"
+    "@umriss-ui/charts": "^0.16.0",
+    "@umriss-ui/core": "^0.33.0"
   },
   "devDependencies": {
     "@fontsource/geist-mono": "^5.3.0",
@@ -65,9 +65,9 @@
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/core": "0.32.0",
-    "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/charts": "0.15.0"
+    "@umriss-ui/charts": "0.16.0",
+    "@umriss-ui/core": "0.33.0",
+    "@umriss-ui/demo": "0.0.0"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",