Changelog

Every release, read live from GitHub. Nothing here is retyped, so it cannot disagree with what is actually published.

How versions are numbered

Semantic versioning, in the usual three parts.

Part	Changes when	What it means for you
major	Something breaks on purpose	A pipeline saved before may need adjusting. The release notes say exactly what and how.
minor	Something is added	Everything that worked keeps working. New cards or parameters appear.
patch	Something is fixed	Nothing changes except that a bug is gone.

The compatibility promise

From 1.0 onward: a pipeline saved on any 1.x version opens on any later 1.x version. Card parameters may be added, never removed or renamed within a major version. A card that has to change incompatibly gets a new identifier, and the old one is marked deprecated with its replacement linked.

Before 1.0, during the beta, that promise does not hold yet. The pipeline file format is still moving. Record the version you ran and archive your pipeline file next to your data. See the migration guides.

Breaking changes

When a release breaks something, the note starts with BREAKING: and it is lifted into its own box above the rest of the notes, both here and in the update banner inside the application. A breaking change buried in a bullet list is a breaking change nobody read.