@umriss-ui/schedule 0.46.0 → 0.47.1

package/CHANGELOG.md

@@ -4,13 +4,13 @@ This document describes what changes for **callers** of the package: exports,
 props, behaviour.
 
 **The numbers.** The middle digit rises when something is added; the last one
-when something is repaired. The six packages are released in step, and a rename
+when something is repaired. The seven packages are released in step, and a rename
 keeps its old name for one further minor, with a warning, before the minor after
 it removes the name ([the upgrade promise, ADR-0066](../../docs/adr/0066-one-number-peers-over-the-minor-a-rename-lives-one-minor.md)).
 Whatever changes existing behaviour stands under a heading "Changed" of its own,
 no matter which digit rose, with a `Migration:` line.
 
-From 0.34.0 the packages share one number - five, and six from 0.40.0, when the dashboard joined: they are released together, and a package without a change of its own still gets a heading for it.
+From 0.34.0 the packages share one number - five, six from 0.40.0, when the dashboard joined, and seven from 0.47.0, when alarms joined: they are released together, and a package without a change of its own still gets a heading for it.
 
 **Release candidates.** The package started as a release candidate under the
 tag `next`. With `0.1.0` it is released: the tag is gone, and the interface
@@ -18,6 +18,19 @@ moves from here under the rule above.
 
 ---
 
+## 0.47.1 – Released in step with the table (Oct. 2026)
+
+No change of its own; the number moves with the table's repaired exports.
+
+## 0.47.0 – Released in step with alarms (Oct. 2026)
+
+No change of its own; the number moves with the new package `@umriss-ui/alarms`.
+
+### Changed
+
+- **The peer ranges move to `^0.47.0`.**
+  - Migration: install the 0.47 version of `@umriss-ui/core` and `@umriss-ui/charts` beside it.
+
 ## 0.46.0 – Zoom keys, and the plan as a table (Oct. 2026)
 
 ### Added

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.46.0
+# @umriss-ui/schedule 0.47.1
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -1666,11 +1666,11 @@ no subtask yet; the caller creates one, with its own identity, from
 
 #### Known limits
 
-- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)).
 - No milestones yet: a point in time on a lane has no mark of its own.
 - A dependency joins two subtasks of one task; dependencies across tasks are not yet possible.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ## Plan
 
@@ -2185,7 +2185,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Subtasks
 
@@ -3049,7 +3049,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - No stacked layout on request yet: an overlap is always drawn offset, as the finding it is.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Dependencies
 
@@ -3349,7 +3349,7 @@ export default function OneHandoverDrawnItsOwnWay() {
 
 ##### Mark the critical path
 
-The planning system works out the critical path and hands over its subtask ids; `muted` takes the rest back so the path reads first. The schedule computes nothing ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)), so the switch only changes what the application marks.
+The planning system works out the critical path and hands over its subtask ids; `muted` takes the rest back so the path reads first. The schedule computes nothing ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)), so the switch only changes what the application marks.
 
 ```tsx
 import { useState } from "react";
@@ -3475,9 +3475,9 @@ type DependencyEnds = "dot" | "none";
 
 #### Known limits
 
-- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)).
+- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Routes
 
@@ -5233,7 +5233,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - One task at a time: there is no multiple selection.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Interactions
 
@@ -6352,7 +6352,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - Only the view is shared - the span and the folded groups, not the selection, the hover or the vertical scroll.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Functions on the hook
 
@@ -6810,7 +6810,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - Overlapping work is marked, not packed into sub-lanes; stacked overlap is not built yet.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ## Editing
 
@@ -7185,10 +7185,10 @@ From `Overlap` — the full table stands on [Findings as data](#findings-as-data
 
 #### Known limits
 
-- No undo: your application owns the data, and with it the history - see [Undo](#undo) ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)).
+- No undo: your application owns the data, and with it the history - see [Undo](#undo) ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)).
 - The keys move work in time only; a lane change needs the pointer.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Undo
 
@@ -7198,13 +7198,13 @@ Taking back the last applied change: the application keeps the plan before each
 import { useSchedule, applyIntent } from "@umriss-ui/schedule";
 ```
 
-The schedule keeps no history: it reports each intent and the application applies it ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)), so the stack of plans is the application's to keep ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)). The key is the page's, not the plot's - the plot leaves Ctrl and ⌘ to it.
+The schedule keeps no history: it reports each intent and the application applies it ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)), so the stack of plans is the application's to keep ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)). The key is the page's, not the plot's - the plot leaves Ctrl and ⌘ to it.
 
 #### Examples
 
 ##### Undo the applied intents
 
-The history is the application's, not the schedule's ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md), [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)): it keeps the plan before each intent it applies, and Ctrl+Z, ⌘Z on a Mac, or the Undo button pops the last one. The schedule only knows end-to-start, so a start-to-start is one dependency with a negative lag: the lag is the delay less the spec's three hours, and the line is drawn apart.
+The history is the application's, not the schedule's ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md), [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)): it keeps the plan before each intent it applies, and Ctrl+Z, ⌘Z on a Mac, or the Undo button pops the last one. The schedule only knows end-to-start, so a start-to-start is one dependency with a negative lag: the lag is the delay less the spec's three hours, and the line is drawn apart.
 
 ```tsx
 import { useState, type KeyboardEvent } from "react";
@@ -7539,7 +7539,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A main time never becomes shorter than one raster step, or a minute without a raster.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Snapping
 
@@ -8398,7 +8398,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A rule that changes while a drag runs is noticed at the drop, not before.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ### Ripple
 
@@ -8683,10 +8683,10 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 #### Known limits
 
-- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md)).
 - A dependency joins subtasks of one task, so work of other tasks is never pushed.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.46.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.47.1/docs/adr/0032-what-umriss-is-not.md).
 
 ## Measuring
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.46.0",
+  "version": "0.47.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",
@@ -59,14 +59,17 @@
     }
   },
   "peerDependencies": {
-    "@umriss-ui/charts": "^0.46.0",
-    "@umriss-ui/core": "^0.46.0",
+    "@umriss-ui/charts": "^0.47.0",
+    "@umriss-ui/core": "^0.47.0",
     "react": ">=19",
     "react-dom": ">=19"
   },
   "devDependencies": {
     "@fontsource/geist-mono": "^5.3.0",
     "@fontsource/geist-sans": "^5.3.0",
+    "@umriss-ui/charts": "0.47.1",
+    "@umriss-ui/core": "0.47.1",
+    "@umriss-ui/demo": "0.0.0",
     "@types/node": "^22.20.2",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",
@@ -75,10 +78,7 @@
     "react-dom": "^19.0.0",
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
-    "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/charts": "0.46.0",
-    "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/core": "0.46.0"
+    "vite-plugin-dts": "^4.3.0"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",