Repository navigation
docs(changelog): record the mirror-order fix and the catch-up run - #5
Merged
Merged
Conversation
The 2026-08-16 entry still tells a reader the refresh runs "Mondays 03:00 UTC", which is the schedule that made the mirror a full cycle stale. Add the 2026-10-13 section: what was wrong (measured), the new slot, the per-run "which build was mirrored" report, and the catch-up run that brought the dataset back onto the live `data_built_at` with 0 of 129 published scores differing. Refs kanban t_23be34f6.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #4 (kanban t_23be34f6). CHANGELOG still told readers the refresh runs "Mondays 03:00 UTC" (the 2026-08-16 entry) — the schedule that made the mirror a full cycle stale. Adds the 2026-10-13 section with the measured before/after and the new slot; no data or workflow change.