Release Notes
What shipped in every release of the platform.
The current release is v1.0.7 (Analytics that aggregate, and column pickers that cannot be wrong). Every change is classified so you can scan for the categories that affect you.
Release policy
Change classification
| Field | Type | Description |
|---|---|---|
| Added | string | New capability that did not exist before. |
| Changed | string | Existing behaviour that now works differently. |
| Performance | string | Same behaviour, materially faster or lighter. |
| Fixed | string | A defect that produced incorrect or failed behaviour. |
| Security | string | A change that closes an exposure, tightens access or hardens defaults. Apply these promptly. |
| Removed | string | A capability that is no longer available. |
| Docs | string | Documentation, examples and reference material. |
Versioning
Versions follow semantic versioning. A major version may change the request or response contract, a minor version adds capability without breaking it, and a patch version fixes behaviour. Pre-release versions were internal previews and were never available to customers.
Release history
| Version | Date | Name | Changes |
|---|---|---|---|
| v1.0.7 | 2026-10-12 | Analytics that aggregate, and column pickers that cannot be wrong | 19 |
| v1.0.6 | 2026-10-11 | Resilient live execution telemetry | 21 |
| v1.0.5 | 2026-10-11 | Demo access, data-source editing and menu dismissal | 18 |
| v1.0.4 | 2026-10-11 | Guided demo and dependency-outage handling | 22 |
| v1.0.3 | 2026-10-10 | Production error handling | 35 |
| v1.0.2 | 2026-10-10 | Account recovery and control-centre depth | 51 |
| v1.0.1 | 2026-10-10 | Launch hardening | 22 |
| v1.0.0 | 2026-10-10 | General availability | 32 |
| v0.9.0 | 2026-09-22 | Hardening and analytics rebuild | 5 |
| v0.8.0 | 2026-08-30 | Multi-tenant foundations | 5 |
What is in the current release
- Added: A grouping stage in the chart engine. Every chart config now carries an **Aggregate** setting - Sum, Average, Number of rows, Minimum, Maximum or None - applied before sorting and the row limit, so `Sort by revenue`, `Descending`, `Take first 10` produces a genuine top-10 list instead of ten rows of the same category. `src/lib/chartData.ts` owns the whole pass (group, sort, limit) so the dashboard, the table and the config preview can never disagree.
- Added: Column discovery for data sources. `DataSource` now exposes a read-only `columns` list, inferred from the stored file (CSV header, newline-delimited or whole-document JSON, spreadsheets) and cached on `config`, so the pipeline builder is still a single list request. The upload preview returns the same list, and a source that cannot be inspected locally - a remote API or a database connection - reports none, which is the signal to fall back to free text rather than offer a wrong menu.
- Added: `has_dataset` on the pipeline API: `true` once any execution has succeeded, read from a single annotated query for the whole list. The analytics picker and, indirectly, the dataset rows endpoint key off it.
- Added: Chart layouts are saved per pipeline and per session mode, so a dashboard survives a refresh without leaking into another workspace, and a demo layout can never appear in a real one. A chart can also be deleted, from the same dialog that edits it.
- Added: `apps/pipeline/test_transformations.py`, the first direct coverage of the transformation engine, pinning the step vocabulary including its aliases and the loud failure modes.
- Changed: A line chart orders its X field ascending unless an explicit sort field is chosen: a time series plotted in storage order zigzags for no visible reason.
- Changed: Axis ticks shorten ISO dates to `Oct 10`, in both bar and line charts, so a crowded date axis stays readable.
- Changed: Analytics reads a 500-row window instead of 100. Grouping happens client-side, so a narrow slice of a transactional feed made every aggregate look like a rounding error.
More resources
Troubleshooting
Fix pipeline, transformation and chart failures.
Case study
How the platform is architected and why.
Last reviewed October 2026.