Where the numbers come from
When the numbers changed
Numbers here move when a new build lands and the pipeline loads it. One line per build, newest first, and only the builds that moved something you could see. A run that loaded the same data again changed nothing, so it gets no line.
Build 25247047 took over from 24575149. 2,036 changes: 16 pals, 6 skills, 2 items, 2,012 other rows.
25247047the pipeline published it on its ownnormalizer version 27
Build 24575149 took over from 24466863. 11,058 changes: 7 items, 3 technologies, 1 paldeck entries, 11,047 other rows.
Written down after the fact. Nobody recorded this publication while it was happening. We put the row together later from the snapshot archive, and it says so instead of passing for a note taken at the time.
24575149a person read the diff and waved it throughnormalizer version 12written down
What this page does not say
51 of the 153 pipeline runs on record cannot be tied to a build by anything that survived. The snapshot archive remembers when a snapshot was built. The file that says what is live right now is overwritten every time, so it remembers nothing else. Those runs happened, they are counted here, and no line above will ever name them.