The purge asked appdetails about every game, 5.3 hours at 9,847, and one
answer was enough to remove one - appdetails has answered success:false
for live games in bursts (2026-09-27).
GetItems now screens the whole catalogue in a few minutes (unknown,
hidden, unlisted, coming soon, not is_free; never type), and
check_game_health() must confirm each flag; "unavailable" is asked again
five minutes later. A failed batch or a network error never reads as
gone, blocklisted games are not asked about, and more than 500 flags or
100 removals stops the run before anything is written. Removals are
logged as before. A notice names earlier removals Steam has since undone.
The dry run on the real catalogue: 8 flagged, 3 removed (the three
unlisted games), 5 kept because appdetails calls them free. Daily now.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sixteen setup-python steps move from '3.12' to '3.15'. codeql.yml alone
stays on '3.14': CodeQL's supported-languages page lists Python up to 3.14
and its extractor runs on that interpreter; the pipeline uses no 3.15-only
syntax.
- The updater-json job of release-desktop.yml sets up 3.15 instead of
running the runner image's python3.
- Four text-mode writes name encoding="utf-8": the dead-link log, both
leaderboards and clear_temp(). 3.15 makes UTF-8 the default (PEP 686); on
Windows an older Python writes cp1252, which cannot encode the
leaderboards' emoji, so those scripts crashed there. CI already wrote
UTF-8, so no committed output changes.
- requirements.txt's compile line and sonar.python.version say 3.15.
`uv pip compile --universal` gives the same lock for 3.12 and 3.15, and
every pin installs on 3.15 with --require-hashes --only-binary :all:
(charset-normalizer's cp315 wheels were already hashed).
Checked on Python 3.15.1: the 299 tests pass with EncodingWarning and
DeprecationWarning as errors; edit_game.py --check and delete_game.py
--check pass; a full save_main(load_main()) on a copy of the data leaves all
36 files byte-identical to HEAD, as on 3.14, so no shard and no index.json
changes when the data jobs move.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The docs had drifted badly from the code. This makes them true.
LICENCE SPLIT. Code stays MIT; the dataset moves to CC BY 4.0 in a new
LICENSE-DATA, which is explicit about what the project cannot license: the
`description` field is the publisher's own store blurb stored verbatim (median
213 characters), `header_image` is a URL to publisher artwork, and game names
are trademarks used nominatively. Blanket-MIT over that material was a claim
the project was never entitled to make. Facts — player counts, review
percentages, platform support — are noted as unownable; the CC BY grant covers
the compilation and the project's own derived fields.
PRIVACY POLICY, rewritten rather than patched. The previous one said "no
backend, no server-side log, no cookies, no server other than GitHub's CDN".
Every clause of that is now false: the site runs on a Cloudflare Worker that
processes IP and User-Agent and keeps operational logs. It also documents the
one honest exception — the Activity page still calls api.github.com and loads
GitHub avatars from the browser, so GitHub sees a visitor's IP there while no
other page does — and lists every localStorage, IndexedDB and Cache Storage key
with why it exists.
SECURITY.md, rewritten. The old one claimed "no executable code, no
dependencies, no backend, no user data" and said there was no contact address,
while four other files publish one. It also told people to report
vulnerabilities in public issues. There is now a real scope (the Worker, the
proxies, D1, Actions secrets, the Tauri signing key), a private channel via
GitHub's vulnerability reporting, and specific things worth probing.
EULA corrected on two counts: it asserted a single MIT licence over everything,
and claimed there is "no installable software" despite the signed desktop and
Android builds. ToS and DISCLAIMER updated for the licence split, the new
domain, and the removal of in-browser editing and GPG signing — the disclaimer
described a signing flow that no longer exists.
README contradictions fixed: 1.2k games -> 3,424 across 5 shards not 2, 11
workflows -> 24, two scripts listed that were never in the tree, a TanStack
Table dependency the project does not use, and nine links to the old Pages URL.
New: docs/DEPLOYMENT.md (how a push becomes a deploy, the two wrangler.jsonc
fields that silently break it, and the stale-service-worker trap when verifying)
and docs/ADMIN.md (Cloudflare Access plus the GitHub App, with the exact
permission set — Contents write and Metadata only, and why Actions and
Workflows are deliberately withheld).
Two live fixes came out of writing this. GitHub Pages was serving a blank page:
it had the new index.html, which references assets at `/`, while Pages serves
under /free-steam-games-list/, so every asset 404'd — and deploy-pages.yml kept
redeploying it. That workflow now publishes a redirect that preserves the #/
fragment, since Pages cannot issue a 301. And CI pinned Python at 3.11, 3.12
and 3.14 across different workflows while the docs claimed 3.12 was pinned;
all fourteen references are now 3.12, which makes the claim true.
TERMS_VERSION 1 -> 2, so everyone re-consents. A privacy policy that now
discloses edge logging where it previously promised none is not a change to
apply silently.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The scheduled pipeline has been failing daily since 2026-08-13 (last successful
`Auto update` was e8b7d1b2). Root cause: `secrets.GH_TOKEN`, a PAT, expired.
Every workflow passing it to actions/checkout dies at fetch with exit 128.
No workflow actually needs a PAT. Each already declares
`permissions: {contents: write}`, so the built-in GITHUB_TOKEN has push rights —
proven by mark-dead-games.yml, the only green data workflow and the only one
with a bare checkout. Removed the `token:` input from all 12 sites. This also
ends the silent-expiry failure mode rather than rescheduling it a year out.
`workflow_run` triggers are unaffected: GITHUB_TOKEN suppression applies to
push/issues/release events, and update-daily.yml plus the three notify-*
workflows all key off workflow_run, which the Actions service emits on run
completion regardless of the checkout token.
Also in this commit:
- ingest-from-issue.yml gated on `author_association`. Without it, any user
could open an issue titled [add-game] and have their JSON committed and
pushed to main with `contents: write`. A title match is not an authorization
check. Its `&&`/`||` commit chain is also parenthesised — left-associativity
meant it pushed even when there was nothing staged.
- bot-ingest.yml's final step deleted. It referenced `secrets.BOT_TOKEN` while
the rest of the file uses TELEGRAM_BOT_TOKEN, `cat`-ed a result.txt no step
creates, ran under `if: always()`, and interpolated a secret straight into a
shell command line. The Python step above it already does the same Telegram
callback correctly. `secrets.BOT_TOKEN` is now unreferenced.
- The snapshot feature is committed. snapshot-daily.yml gains the
`concurrency: {group: data-write}` guard every other data-writing workflow
has — without it a 23:00 run can push against jobs that take ~2 hours. The
`pip install requests` in bash/snapshot.sh is dropped: snapshot.py and
scripts/core/* import only stdlib.
- New web-ci.yml. deploy-pages.yml was the only thing running `npm run
typecheck`, so deleting it during the Cloudflare migration would leave the
frontend unchecked. Uses a plain `npm ci` — the old `npm ci || npm install`
fallback is what let the lockfile conflict above go unnoticed.
- New dependabot.yml. NOTE: an in-repo config replaces the one in repo
settings and supersedes open PR #111. Groups security updates so the
transitive backlog collapses into one PR instead of one per package.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Detects online games released >1 year ago whose current_players hits 0
across consecutive runs. After 14 days of zero-player observations the
game is flagged with `is_dead: true` and "💀 Dead game" appended to notes
(idempotent).
- scripts/mark_dead_games.py: standalone script with --dry-run / --days
flags. Uses zero_player_since timestamp (robust against schedule drift)
rather than a streak counter.
- .github/workflows/mark-dead-games.yml: cron 0 30 4 * * 1,4 (Mon + Thu
04:30 UTC, after Sun/Wed top-online refreshes player counts).
- scripts/core/data_store.py: extend SKELETON_TEMPLATE with `is_dead` and
`zero_player_since`; lazy migration via existing migrate_record loop.
Add `append_note_idempotent()` helper.
- scripts/check_dead_links.py: refactor to use append_note_idempotent so
reruns don't accumulate duplicate "💀 Delisted" notes.
- web/src/lib/schema.ts: mirror new fields on GameRecord and
SKELETON_TEMPLATE.
- web/src/stores/filters.ts: add `hideDead` toggle.
- web/src/pages/Games.tsx: filter-bar checkbox to hide dead games.
- web/src/components/games/GamesTable.tsx: 💀 emoji prefix on dead rows;
apply hideDead filter.
- en.json / vi.json: `games.hideDead` ("Hide dead" / "Ẩn dead").
- All data-mutating workflows now share `concurrency: data-write` to
prevent races on `git push` to data/. bot-ingest moved from its own
group to the unified one.
- notify-ci-failure list extended with "Mark Dead Games".
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>