@pond-ts/react 0.19.0 → 0.21.0

package/CHANGELOG.md

@@ -7,12 +7,83 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 file covers both packages. Pre-1.0: minor bumps may include new features and
 type-level changes; patch bumps are strictly additive.
 
-[Unreleased]: https://github.com/pjm17971/pond-ts/compare/v0.19.0...HEAD
+[Unreleased]: https://github.com/pjm17971/pond-ts/compare/v0.21.0...HEAD
+[0.21.0]: https://github.com/pjm17971/pond-ts/compare/v0.20.0...v0.21.0
+[0.20.0]: https://github.com/pjm17971/pond-ts/compare/v0.19.0...v0.20.0
 [0.19.0]: https://github.com/pjm17971/pond-ts/compare/v0.18.0...v0.19.0
 [0.18.0]: https://github.com/pjm17971/pond-ts/compare/v0.17.1...v0.18.0
 
 ## [Unreleased]
 
+## [0.21.0] — 2026-06-11
+
+### Added
+
+- **`TimeSeries.mapColumns({ col: (value) => newValue })`** — a per-cell column
+  value transform. The column-scoped counterpart of the event-based `map()`:
+  where `map(schema, event => newEvent)` rebuilds whole rows through an
+  arbitrary closure (and can change the schema/key), `mapColumns` transforms
+  individual columns' values in place, reading the columns directly (no
+  per-row `Event`) so it stays on the fast columnar path. Same kind in/out
+  (number→number, string→string, …), so the schema is unchanged; missing cells
+  carry (the mapper isn't called on `undefined`). ~5–6× faster than the
+  `map()` workaround on a build → transform → read pipeline.
+
+### Changed
+
+- **`select` / `rename` / `slice` / `cumulative` / `diff` / `rate` /
+  `pctChange` / `fill` / `shift` / `collapse` are now column-native.** They
+  reshape the columnar store directly instead of materializing events, so the
+  columnar construction win is preserved through these transforms — build →
+  transform → read pipelines run several× faster (~7–10× for `select` /
+  `rename` / `slice`; ~5–7× for the `cumulative` / `diff` / `rate` / `fill` /
+  `shift` / `collapse` folds). No API change for type-correct callers (one
+  narrow `fill` behavior change is noted under Fixed). `cumulative` / `diff` /
+  `rate` / `pctChange` / `fill` / `shift` / `collapse` are also the first
+  operators extracted into `batch/operators/` (internal refactor); `fill`
+  rebuilds only the columns it actually changes; `slice` normalizes
+  `Array.prototype.slice` semantics onto a zero-copy `withRowRange` reshape;
+  `collapse` reads only the keyed columns and passes the kept columns through
+  by reference.
+
+### Fixed
+
+- **`rename` now rejects target-name collisions** (e.g. renaming `a` → `b`
+  when `b` already exists) with a clear error, instead of silently producing a
+  duplicate-named schema. Also fixes a prototype-chain bug where a column named
+  `toString` (or another `Object.prototype` member) could be corrupted during
+  a rename.
+- **`fill` now throws on a kind-mismatched literal** (e.g.
+  `fill({ value: 'banana' })` where `value` is numeric — type-allowed because
+  mapping values are the broad `FillStrategy | ScalarValue`) with a clear
+  `RangeError` naming the column, instead of silently producing an
+  internally-inconsistent series (the old events path returned the literal
+  from `.get()` while the numeric column read `NaN`). The throw is
+  gap-dependent — it only fires when the literal would actually be placed.
+
+## [0.20.0] — 2026-06-04
+
+Two internal performance improvements driven by the dashboard experiment at
+256-host stress. **No public API changes** — both are behavior-preserving.
+
+### Changed
+
+- **Column-native partition routing.** `partitionBy(...)` over a strict
+  time-keyed source now routes its source chunks into per-partition
+  **chunked** sub-series via a coalescing staging tier, replacing the
+  per-partition `Event[]` retention. A large drop in retained memory and
+  object count at high partition counts (gRPC bench at 256 partitions: 60×
+  fewer columnar stores, −99.4% `Event` retention, +24% sustained throughput)
+  ([#175](https://github.com/pjm17971/pond-ts/pull/175)). Behavior-preserving;
+  internal only — no public surface added.
+- **`LiveView.toTimeSeries()` snapshot caching.** The built `TimeSeries` is
+  memoized against an internal mutation counter, so back-to-back
+  identical-state calls (multiple subscribers, framework commit batching,
+  StrictMode double-invoke) return the cached instance by reference instead of
+  rebuilding the whole snapshot — ~44 ms → ~0 at a 262k-event window. A
+  fresh-state call still builds; safe because `TimeSeries` is immutable
+  ([#180](https://github.com/pjm17971/pond-ts/pull/180)).
+
 ## [0.19.0] — 2026-06-02
 
 Adds an **experimental column-read surface to the live side** — read typed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pond-ts/react",
-  "version": "0.19.0",
+  "version": "0.21.0",
   "description": "React hooks for pond-ts live time series",
   "license": "MIT",
   "repository": {
@@ -32,7 +32,7 @@
     "test:runtime": "vitest run"
   },
   "peerDependencies": {
-    "pond-ts": "^0.19.0",
+    "pond-ts": "^0.21.0",
     "react": "^18.0.0 || ^19.0.0"
   },
   "devDependencies": {