Dataset updates are paused — data is current to 6 July 2026

[dcaribou]

Status: automated updates are not running. The dataset is stale and there is
no estimated date for updates to resume.

What happened

The automated pipeline that collects data for this project stopped completing
successfully in mid-July 2026. The last successful collection run was on
10 July, and the last data update was published on 11 July. Since then the
collection step returns no data, and every scheduled run has failed.

This is not a bug in the project's code, and nothing on our side changed. The pipeline depends on pages from the upstream source that are no longer reliably reachable from GitHub Actions runners.

What this means for the data

The published dataset is complete and internally consistent, but frozen:

• games and game_events — nothing after 2026-07-06
• appearances — nothing after 2026-06-28
• player_valuations — nothing after 2026-06-12
• players — no squads beyond last_season 2025, so 2026/27 squads are not covered
• transfers — contains transfers that were already announced as of 11 July,
  including ones dated into 2026/27, but nothing recorded after that date. Treat
  the 2026 summer window as incomplete, not absent

Everything published before the stall is unaffected and remains available. The
DuckDB file, the CSVs on R2 and the Kaggle dataset all still work, and the
Kaggle copy is up to date with the most recent successful build (5 August),
including the player-valuations correction from #378.

If you have automated ingestion pointed at this dataset it
is reading a snapshot that has stopped moving. You may want to pause scheduled
pulls until this thread says otherwise.

Will this be fixed?

I don't have an answer I'd trust enough to publish. This is a free project I
maintain in my spare time, and the constraint here isn't one I can resolve by
spending an evening on it. I would rather tell you plainly that updates are
paused indefinitely than post a date I end up missing.

I'll update this thread if anything changes. Please don't open new issues asking
for an ETA — I'd only be repeating this post. Reports of quality problems in
the existing data are still welcome and still get fixed.

Thanks to everyone who reported this, and sorry for the silence while I worked
out what was going on.

[frankostyn]

OK David, thx for the update.
And thx for all the work you put into this.
All the best.
Frank