Release history
What changed
Trackers publish a snapshot, not a history. Every time a new release is loaded here, it is compared with the one before and the differences are written down: projects that appeared or vanished, statuses that moved, capacities that were revised, ownership that changed hands.
No comparisons yet. The change log fills the first time a new tracker release is ingested over an existing one: the previous database is kept, the two are diffed, and the result is committed to the repository. Until then there is nothing to compare against.
How this is produced
Each ingest keeps the outgoing database before replacing it. A diff script then compares the two on identity, not on name, using the tracker's own asset identifiers, so a renamed project is recorded as a rename rather than as one asset vanishing and another appearing.
Only meaningful moves are recorded: an asset appearing or disappearing, and changes to status, capacity, ownership, name, key dates, containment, propulsion, or whether a pipeline has a route. Capacity moves below a rounding threshold are ignored. Every change is written as a sentence at diff time, so these pages never have to reconstruct one from raw fields.
The output is committed to the repository, which means the history survives even though the tracker itself only ever publishes a current snapshot.