diff --git a/.gitattributes b/.gitattributes index e88615dc..43931597 100644 --- a/.gitattributes +++ b/.gitattributes @@ -17,6 +17,7 @@ CONTRIBUTING.md export-ignore SECURITY.md export-ignore ACCESSIBILITY.md export-ignore CHANGELOG.md export-ignore +changelog/ export-ignore README.md export-ignore # The legal documents stay IN the archive: the web build reads all of them # (web/build/legal-versions.ts) and stops when one is missing. diff --git a/CHANGELOG.md b/CHANGELOG.md index 41cf0d48..83c63ff1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,13 @@ All notable changes to this awesome noob repo will be documented here. +Every release has its own file in [`changelog/`](changelog/): +`changelog/v/..x/.md`, for example +[`changelog/v4/4.7.x/4.7.1.md`](changelog/v4/4.7.x/4.7.1.md). Pre-releases +go to [`changelog/beta/`](changelog/beta/) - none has been published. What is +not released yet is under [Unreleased] below; a release moves it into its own +file and adds the release to the table of its major version. + ## [Unreleased] ### 🔒 Security @@ -75,2105 +82,64 @@ refreshes the list every day, and the site and the apps stay up. `knip.json` now ignores unlisted dependencies in `tsconfig.json` alone. Again no advisory and no change in behaviour, so no release. -## [v4.7.1] – 2026-11-09 (The "Curb Cut" Edition) +## v4 -An accessibility release. The repository gains an accessibility statement -that says honestly what works with a keyboard, a screen reader and zoom, and -what does not yet. The worst barriers it found are fixed: -- the games table is a real table to a screen reader; -- the first-run screens hold the keyboard focus; -- kernel-level anti-cheat is no longer told apart by colour alone; -- both themes meet the contrast WCAG asks for; -- the desktop app zooms. - -Like a curb cut, most of it helps everyone. The community docs were also -brought back in line with the repository. No legal document you accept -changed, so nobody is asked to accept the terms again. - -Desktop and Android go from `2.5.0` to `2.5.1`, and the repo's public version -from `4.7.0` to `4.7.1`. The desktop app offers 2.5.1 through its updater once -the release is published. On Android, install the new APK over the old one. - -### ✨ Added - -- **An accessibility statement.** `ACCESSIBILITY.md` says what works today - with a keyboard, a screen reader and zoom, and what does not work yet: the - games table, most charts, the first-run screens, zoom in the apps. It also - lists which browsers and apps are checked by hand, and how a report is - handled. GitHub shows it as the repository's Accessibility tab. Barriers get - their own issue form and an `accessibility` label, and the About page links - the statement and the form. -- A pull request template covering what and why, the checks to run, and a - short accessibility list for interface changes. - -### 🐛 Fixed - -- The About page's stack list said SvelteKit 2 and counted 3,600 rows. Its - footnote said everything the page loads comes from this site, which is not - true of Cloudflare's beacon and human check. It now says what is true: the - game data and art come from this site. The Vietnamese AI note gains the - sentence it was missing. -- Source archives (`git archive`, GitHub's "Source code" downloads) left out - three legal documents that the web build reads, so building from one - stopped. They are included now. -- **Accessibility**, on the website and in the apps from 2.5.1: - - **The games table** is now a table to a screen reader. It exposes its - roles, the row and column counts, and a position for every row, even - though only the rows on screen exist. The image, data-issue and Steam - columns have names. - - **Table rows** are no longer a link wrapped around another link, and each - row is one Tab stop instead of two. Clicking anywhere on a row - still opens the game. - - **The phone cards** are a list that tells a screen reader its length and - each card's position. - - **The terms screen and the human check** are dialogs that take focus, and - the page behind them is out of reach until you are through. Before, Tab - walked through the hidden page first, and Ctrl/⌘+K could open the - command palette underneath them, out of sight but holding focus. - - **Kernel-level anti-cheat** shows a shield icon and the words, not only a - red badge. - - **Contrast:** - - Light-theme links, primary buttons, warnings and badges reach 4.5:1. - The light theme's amber is a shade darker as a result. - - Red badges in the dark theme reach 4.5:1 too. - - Text boxes and drop-downs have a visible 3:1 edge in both themes. - - **Zoom:** - - The games list keeps a minimum height when zoomed in, instead of - shrinking to nothing at 300-400%. - - The desktop app zooms with Ctrl/⌘ and + / −. - - **Smaller fixes:** - - "Back to top" is out of the Tab order while it is hidden, and jumps - instead of gliding when *reduce motion* is on. - - The command palette's search box shows a focus ring. - - Screen readers read out the 💀 and the table's warning icon as words. - - `ACCESSIBILITY.md` moves all of this from "Known limitations" to "What - works today". - -### 🧰 Tooling & misc - -- `web/src/lib/a11y.test.ts` holds those fixes in the code. It also computes - the theme's contrast with the WCAG formula, so a colour edit that drops - below 4.5:1 for text, or below 3:1 for a control's edge, fails the tests. - -### 📚 Docs - -- The community docs match the repository again: - - **README:** live game-count and version badges, SvelteKit 3, every desktop - package, the shard layout, the workflows its table left out, and which - commits deploy. - - **SECURITY.md:** the real stack, pushes with the built-in token, and the - media host and the ingest and update endpoints in scope. - - **AUTHORS.md, `username.txt`, CONTRIBUTING.md and the code of conduct.** - - **The issue forms:** the hash links, GitHub Pages permalinks and the - editing and GPG options are gone. The version is under the title, not - behind a hover. - - **`web/README.md`, `docs/dev_env.md` (EN + VI), the acknowledgements and - the contact page.** Neither of the last two is a document you accept, so - nobody is asked to accept the terms again. -- `CLAUDE.md`: `ACCESSIBILITY.md` is a claim about the code, kept true in the - same pull request, and the rules behind the accessibility fixes. - -## [v4.7.0] – 2026-11-03 (The "Lucky Dip" Edition) - -Two small additions. A Random games page picks up to five games from the -catalogue when you cannot decide what to play, and the first-run terms screen -gets a way out: on the website, "Leave site" takes you back to the page you -came from; in the apps, Decline now quits, which on Android it never did. No -legal document changed, so nobody is asked to accept the terms again. Desktop -and Android bumped `2.4.1` → `2.5.0`; repo public-facing version `4.6.1` → -`4.7.0`. The desktop app offers 2.5.0 through its updater once the release is -published; on Android, install the new APK over the old one. - -### ✨ Added - -- **Random games.** `/random`, in the sidebar, the menu and the command - palette, with a dice button on the dashboard, rolls one to five games (five - to start with): online, offline or either, dead games only when you ask for - them, and never one marked unsafe. Roll again for a set that avoids the - games on screen; a smaller count keeps the first ones, a larger one adds to - them. Opening a game and coming back keeps the picks, and nothing is - stored: a reload rolls anew. -- **Leave site**, on the first-run terms screen and on the notice after - Decline (website only). A page may not open the browser's own start page, - so it goes back to the page before the site - the new-tab page when you - typed the address there, the search results when you came from a search - - past every page of the site you opened in between. When the site is the - first page in its tab, it says so and offers to close the tab; that takes a - second click, because closing the last tab closes the browser window too. - -### 🐛 Fixed - -- Declining the terms quits the Android app. It did nothing at all: the app - asked its window to close, which does nothing on Android. Both apps now quit - through Tauri's own exit, and the declined notice appears if an app is ever - still open afterwards. The apps also drop a permission nothing uses any more - (closing a window from script) for the one quitting needs. - -### 🧰 Tooling & misc - -- Dependencies: SvelteKit 3.1.1 and adapter-static 4.0.1, Svelte 5.57.3, - the Tauri shell plugin 2.6.0 (JavaScript and Rust together) and - single-instance 2.5.5, the updater's JavaScript side 2.14.1 (its Rust side - already was), wrangler 4.156.0, pytest 9.2.0 and the SonarCloud scan - action 8.4.0, plus patch releases of the icon, toast and virtual-list - libraries. No security advisory among them; nothing changes in how the - site or the apps behave. -- The undici override is gone: wrangler 4.156.0's local simulator pins the - patched undici 7.30.1 itself. - -### 📚 Docs - -- `CLAUDE.md`: how `/random` rolls and why it stores nothing; how Leave site - finds the page before the site, and why Decline quits through `exit()`. -- Both READMEs list the random page and its modules. - -## [v4.6.1] – 2026-10-31 (The "Zip Tie" Edition) - -A security pass. The desktop app's updater takes the patched zip reader -v4.4.1 had to leave waiting on Tauri, and the service-worker build takes -patched glob and minimatch. Nothing -changes in how the site or the apps look or behave. Desktop and Android -bumped `2.4.0` → `2.4.1`; repo public-facing version `4.6.0` → `4.6.1`. -The desktop app offers 2.4.1 through its updater once the release is -published; on Android, install the new APK over the old one. - -### 🔐 Security - -- **The desktop updater's zip reader is patched.** tauri-plugin-updater - 2.14.1 moves from zip 4 to zip 9.2, which closes six advisories in how an - archive is read and extracted, one of them critical: two headers in one - archive that disagree, so whatever checks an archive and whatever unpacks - it could see different files. The others are symlinks pointing out of the - destination, setuid bits and permissions carried through symlinks, an - unbounded symlink target, and an AES entry accepted without its - authentication code. The updater opens a zip only on Windows, and only - after it has checked the download's signature, so a forged archive never - reached it. Still waiting on Tauri: the Linux GTK 3 bindings (glib 0.18) and the unmaintained - proc-macro-error, zbus_names and zvariant. -- Build tooling: glob 14.0.3 and minimatch 11.0.3 in the service-worker - build, two moderate advisories published on 2026-10-30 (an aborted walk - that kept reading directories, and patterns that could take exponential - time). Only this repository's own patterns reach them, at build time; the - service worker precaches exactly the same 172 URLs as before. -- deepmerge, used by the Svelte and rollup plugins to merge their own - configuration at build time, has a low advisory with no fixed release. It - never ships to the site, the Worker or the apps, and the alert is - dismissed as a tolerable risk. - -### 📚 Docs - -- `CLAUDE.md`: the glob and minimatch overrides, why they are safe and when - to delete them; the undici override can go with wrangler 4.156.0. - -## [v4.6.0] – 2026-10-30 (The "Polyglot" Edition) - -The catalogue now takes free games in every language, not only the ones -that support English: about 1,300 more, most of them Chinese, Japanese or -Korean, arrive through the review queue over the next days. The site and -the apps get a language filter, search that matches across scripts and -widths, and CSV files that Excel opens correctly; and 1,357 games filed under -"Free To Play" get a real genre. Desktop and Android -bumped `2.3.0` → `2.4.0`; repo public-facing version `4.5.1` → `4.6.0`. -The desktop app offers 2.4.0 through its updater once the release is -published; on Android, install the new APK over the old one. - -### ✨ Added - -- **Games in every language.** Discovery used to search Steam only for free - games that list English, which left out 1,592 of them: mostly Simplified - Chinese (784), Japanese (317), Korean (165) and Traditional Chinese (164) - only, the free Japanese visual novel `//トロイメライ・ノクターン` among them. - It now proposes every free game whatever its languages, and every release - window swept before gets one more pass. The pipeline still asks Steam in English, so - tags, genres and language names stay in English; a name or description the - developer never wrote in English stays in their language. -- **A language filter on Games**, counted like the others and part of the - link (`?lang=Japanese`), so a reader can keep to the languages they read. - The About page says the catalogue now covers every language. -- **Search across scripts and widths.** Every search box (Games, the command - palette, developers, publishers and the anti-cheat list) now matches - half-width and full-width forms and hiragana and katakana as one: `トロイ`, - `とろい` and `トロイ` find the same game, and `4` finds `4`. One kanji, kana - or Hangul syllable is enough in the command palette. -- `/admin` shows a candidate's languages, with a **No English** badge when - English is not among them. Such games are decided like any other. - -### 🐛 Fixed - -- The header search no longer jumps to Games in the middle of a word typed - with a Japanese, Chinese or Korean input method; it waits until the word is - chosen. And it keeps its focus when it does jump: until now the next letter - typed after the jump went nowhere, whatever the language. -- A CSV export opens in Excel with its Japanese, Chinese and Korean names - intact (it now starts with a byte order mark). -- A long Chinese or Japanese description is cut at the end of a sentence - where it can be, and never ends in `、…` or `。…`. -- **"Free To Play" is no longer a genre.** Steam spells it with a capital T, - the list of names never to use as a genre had a small one, and 1,357 games - were filed under "Free To Play" - the third most common genre, and one that - says nothing about a catalogue of free games. New games get their real - genre, and the daily store refresh gives the 1,357 theirs from Steam, 150 a - day (about nine days). A genre someone set by hand is never touched. -- A queued store link written in full-width digits (`5118700`) is read - as the appid it is; digits of any other script are refused. Such an appid - used to slip through, and the next daily refresh would have stopped on it. - The blocklist now accepts exactly the lines the site's own reader does. - -### 🧰 Pipeline - -- Discovery runs wait in turn: backfill windows dispatched together no longer - cancel each other, and a window can be swept a whole year at a time - (`max_pages`). Each run says how many candidates do not list English. - -### 📚 Docs - -- `docs/plan/19-all-languages.md`: what kept these games out, what every - workflow does with them, and what is left (games not sold in the US, CJK - fonts). - -## [v4.5.1] – 2026-10-27 (The "Speed Bump" Edition) - -The site's Worker now limits how fast one address can call it, behind -Cloudflare's own rate-limiting rule at the edge. Nothing changes for readers, -the apps or the pipeline: every limit sits far above what they send. The -desktop and Android apps stay at `2.3.0`, with no new build. Repo -public-facing version `4.5.0` → `4.5.1`. - -### 🔐 Security - -- **Rate limits in the Worker, one budget per surface.** Per address and per - minute: the catalogue API 240 requests (loading the whole catalogue takes - about 16), the image proxy 600, the other public API routes 120, the human - check 20 (a person sends one a day) and the admin surface 300. Past a limit - the Worker answers `429 Too Many Requests` with `Retry-After: 60` until the - minute is up; the apps can read that answer, where they would otherwise have - seen a network error. An IPv6 address counts by its /64, the block one - subscriber is normally given. Cloudflare keeps these counts per server, so - they stop a client that keeps its connection open, as browsers and most - scripts do; one that reconnects for every request is left to the edge rule, - which counts exactly. They are ceilings for abuse, never quotas. The limits - are bindings in `web/wrangler.jsonc` and change by pull request. -- **Two layers, the edge first.** The zone's rate-limiting rule still refuses - a burst before the Worker runs, at no cost, and is the only limit on the - pages themselves; the Worker adds the one-minute window the Free plan's - 10-second rule cannot, and keeps holding if that rule is changed. If the - Worker's limiter is ever unavailable, requests go through rather than fail. -- The recommended edge rule now covers the whole site except the hashed - JavaScript and CSS bundles, at 250 requests per 10 seconds per address. That - is about twice what a first visit sends once the offline cache fills in - (counted from the build: 110 to 130 requests in a few seconds). Applying it - is a Cloudflare dashboard change, described in `docs/SECURITY_SETUP.md` §3a. - -### 📚 Docs - -- `docs/SECURITY_SETUP.md` §3 describes both layers, how to check each one - with `curl`, and the Free-plan rule budget as it stands (one of one rate - limiting rule, four of five custom rules). -- `CLAUDE.md` records the layer's rules: it fails open, is not logged, keeps a - 60-second period and an account-unique `namespace_id` per binding, and needs - a budget for any prefix the Worker runs first for. - -## [v4.5.0] – 2026-10-26 (The "Groundwork" Edition) - -The site and the apps move to SvelteKit 3, the framework every page is -built on. Nothing about how they look or work should change: every page, -the Content-Security-Policy and the offline cache were compared with a -SvelteKit 2 build of the same commit before the switch. The apps also take -Tauri 2.12.5. Desktop and Android bumped `2.2.2` → `2.3.0`; repo -public-facing version `4.4.1` → `4.5.0`. The desktop app offers 2.3.0 -through its updater once the release is published; on Android, install the -new APK over the old one. - -### 🧹 Changed - -- **The site and the apps build on SvelteKit 3** (3.1, with adapter-static - 4). Nothing changes for readers: the same pages with the same text, the - same Content-Security-Policy and the same service-worker precache, each - checked against a SvelteKit 2 build of the same commit. SvelteKit 3 refuses - `svelte.config.js`, so its options moved to `web/build/sveltekit-config.ts`, - now with tests for both the web and the app policies; `$lib` imports became - `#lib`, and the `/legal/` matcher moved to `web/src/params.ts`. -- The service worker is wired into the build by `web/build/pwa.ts`, on - vite-plugin-pwa: `@vite-pwa/sveltekit` never supported SvelteKit 3. -- An old `/#/…` link to a page that no longer exists now opens the "Page not - found" page (`/error/404`); SvelteKit 3 refuses to navigate to it in place. - One that names another site (`/#//other.example/…`) is ignored. -- SvelteKit now asks the site for its version (`/_app/version.json`, a few - bytes) when a tab regains focus and once an hour, where it used to ask only - after a navigation failed. A newer deploy still changes nothing until a - navigation fails, which then reloads the page, as before. -- The desktop and Android apps take Tauri 2.12.5 (tauri-build 2.7.4). - -### 🔐 Security - -- The two SvelteKit advisories dismissed in v4.4.1 (GHSA-27mw-82g8-phjj, - GHSA-pfhg-q3qv-9q6r) are fixed by the upgrade, and `npm audit` reports - nothing: the `cookie` override SvelteKit 2 needed is gone. - -## [v4.4.1] – 2026-10-26 (The "Tune-Up" Edition) - -A dependency and security pass. The desktop and Android apps take the -patched TLS stack their updater talks to the release server with; the dev -tooling, the Python pipeline and the CI workflows catch up with their -fixes. Nothing changes in how the site or the apps look or behave. Desktop -and Android bumped `2.2.1` → `2.2.2`; repo public-facing version `4.4.0` → -`4.4.1`. The desktop app offers 2.2.2 through its updater once the release -is published; on Android, install the new APK over the old one. - -### 🔐 Security - -- **The apps' TLS stack is patched.** rustls 0.23.46 closes four advisories, - among them an unauthenticated ServerHello that could downgrade later - connections to classical key exchange; rustls-webpki 0.103.16 and - webpki-root-certs 1.0.11 stop accepting certificates chained to the - distrusted emSign intermediates. In the apps this is the HTTPS the updater - checks for, and downloads, a new version over. -- Also in the apps: tokio, anyhow and event-listener (soundness fixes) and - plist 1.10, whose quick-xml 0.42 closes two denial-of-service advisories. - Still waiting on Tauri: the zip 4 inside its updater plugin (three - extraction advisories; the updater checks every download's signature - before it opens it), the Linux GTK 3 bindings (glib 0.18) and the - unmaintained proc-macro-error, zbus_names and zvariant. They go when Tauri - moves. -- Dev tooling: undici 7.30.1 inside wrangler's local simulator (three - advisories; it runs in `wrangler dev` and the deploy check, never in the - deployed Worker), zod 4.6.7 (in the unused-code report). -- Two SvelteKit advisories are fixed only in SvelteKit 3 and need code this - site does not have - a prerendered page forwarding an untrusted - `cache-control` to `setHeaders`, and `use:enhance` form actions - so they - are dismissed as not applicable. The move to SvelteKit 3 is a migration of - its own. - -### 🧹 Changed - -- Pipeline: certifi 2026.10.23 (the CA bundle the scrapers verify Steam - with), coverage 7.17.0 for the tests, both pinned with their hashes. -- Site and apps: bits-ui 2.20.2, Lucide 1.61.0, TanStack Virtual 3.13.48, - Vite 8.3.5; tooling: wrangler 4.152.0, knip 6.43.0, Tauri CLI 2.12.4. -- Merged by Dependabot since v4.4.0 and first shipped in these apps: Tauri - 2.12.4; in the build tooling, fast-uri 3.1.9 and serialize-javascript 7.1.4 - (two advisories). -- CI: every workflow runs on `actions/checkout` v6 and `actions/setup-python` - v6. The data jobs still on the Node 20 majors printed a deprecation warning - on every run. The release workflows take rust-cache 2.9.3. - -### 📚 Docs - -- `CLAUDE.md`: the undici override and when to delete it; why SvelteKit - stays on 2 and what would make the two advisories apply again. - `.github/dependabot.yml`: why checkout and setup-python majors are taken by - hand, for every workflow at once. - -## [v4.4.0] – 2026-10-23 (The "Headroom" Edition) - -The data pipeline grows with the catalogue again. With almost 10,000 games -and a few hundred more every day, the jobs that asked Steam about one game at -a time had run out of time; they now read Steam's store API fifty games a -request, wait their turn instead of cancelling each other, and stop in time to -save. The release also carries the tooling merged since v4.3.3 - TypeScript -7, Node 26 and Python 3.15, SonarCloud in CI, the desktop updater fix - and a -certifi bump. The desktop and Android apps stay at `2.2.1`, with no new -build. Repo public-facing version `4.3.3` → `4.4.0`. - -### 🧰 Pipeline - -- **The data jobs scale with the catalogue again.** With almost 10,000 games - and a few hundred more every day, three jobs that asked Steam about one - game at a time had reached GitHub's six-hour limit: on 2026-10-23 Update - Reviews was stopped at exactly six hours with nothing saved. The full - assessment, with every measurement, is `docs/plan/18-pipeline-scale.md`. -- **Reviews come from Steam's store API, for every game, every day.** Fifty - games a request, about two minutes for the catalogue, instead of every two - days and five and a half hours. The percentage is now Steam's own, which - rounds down: about 4,000 games show one point less once (Counter-Strike 2 - "85%" instead of "86%"), exactly as on their store pages. A summary that - says 0 reviews is double-checked game by game before it replaces a - percentage. -- **New games get their reviews again.** Steam's per-game reviews endpoint - has answered with a redirect to the store front since 2026-10-23, so the 38 - games added that day were listed with "N/A". A new game now takes its - summary from the store API when that endpoint gives none, and a game never - read becomes "No reviews" until Steam counts its first one. -- **The daily purge needs two answers to remove a game.** Steam's store API - screens every game in a few minutes, and a game is removed only when - appdetails agrees; "unavailable" is asked twice, five minutes apart. A run - that would remove more than 100 games, or flags more than 500, stops before - writing anything. It also lists earlier removals that Steam has since - undone. It runs daily now, instead of a five-hour sweep on Mondays. -- **Check Dead Links is retired.** In its whole life it never found a dead - link: Steam sends a delisted game's page to the store front, which answers - 200. The purge's screen sees delisted games (`unlisted`) instead. -- **No run is cancelled for waiting.** The data jobs share one queue that - used to hold a single waiting run: a third job cancelled it, and Update - Reviews lost five of ten runs that way. The queue now holds them all, first - in, first out, and every job checks out the latest `main` when it starts - - Auto Update JSON failed four days in ten from working on the data as it was - when the run was queued. -- **Every long job stops in time to save.** Each workflow gives its job a time - budget below its timeout: past it the job saves and commits what it did - instead of being stopped with nothing, and it warns before the budget gets - tight. The leaderboards skip the pauses meant for store pages (Top Online - ~27 minutes instead of 48). The store-data and all-time-peak rotations - stretch their cycle as the catalogue grows instead of their daily runs. -- **Force Re-fetch runs in parts** (`1/8` … `8/8`, queued one after another), - and a game whose fetch fails keeps its old data. - -### 🧰 Tooling - -- **Desktop releases keep reaching the updater.** tauri-action v1 writes each - file's API address into `latest.json`, which the app's update check refuses, - so desktop 2.2.1 had to be fixed by hand before installed apps were offered - it. A new step of the release workflow now rewrites those addresses to the - release's own downloads, checking every signature on the way. -- **SonarCloud reads tests as tests**, and no longer analyses the dataset, - the Android resources the Tauri CLI generated, or the SQLite migrations its - PL/SQL analyser misread. -- **SonarCloud analyses in CI.** A workflow runs the scan on pull requests and - on `main` in place of SonarCloud's automatic analysis, with its settings in - `sonar-project.properties` (formerly `.sonarcloud.properties`). Commits that - only carry data are not scanned. It runs both test suites with coverage - first (pytest-cov for the pipeline, `npm run test:coverage` for the web - app), so SonarCloud shows what the tests reach instead of reading 0%. -- **TypeScript 7, Node 26 and Python 3.15.** The type-check runs on - TypeScript 7, the native compiler: `tsc` for the Worker, the tests and the - admin's Node code, and `svelte-check --tsgo` for the app. TypeScript 6 stays - installed beside it, because svelte-check and SvelteKit's route types still - need the JavaScript API that 7.0 does not have (the admin's svelte-check - stays on it too). CI, the release builds and Cloudflare's build run Node 26, - the LTS from 28 October; the pipeline, its tests and every data job run - Python 3.15, which writes the shards byte for byte as 3.12 did - no - re-download for anyone. The leaderboards and the dead-link log name their - encoding, so they no longer crash on Windows under an older Python. A new - test fails when one of the version pins drifts from the others, and Web CI - now runs on workflow-only changes so it sees them. The full assessment is in - `docs/plan/16-toolchain-2026.md`; `docs/plan/17-typescript-7.1.md` prepares - the move to TypeScript 7 alone once 7.1 is out. - -### 🔐 Security - -- **certifi 2026.10.19** (GHSA-6q48-6c7w-9gw2), the CA bundle behind every - HTTPS request the pipeline makes. eMudhra's `emSign ECC Root CA - G3` had - intermediates whose private keys were compromised; certifi 2026.10.18 - the - version pinned here - had already dropped every emSign root, and 2026.10.19 - puts back the three that are not affected (G1, C1, ECC C3) while G3 stays - out. So the pipeline was never trusting the bad root, but the advisory's - range covered 2026.10.18 and pip-audit flagged it; the lock now names the - fixed release, with its hashes. - -## [v4.3.3] – 2026-10-19 (The "Locksmith" Edition) - -The one open code-scanning alert is fixed, and what SonarCloud found on -`main` is fixed or accounted for: CI installs only what it has pinned and runs -no dependency's install code, the Android app stops copying its data into -Google's backup, and the parsers lose the regexes that could backtrack. -Desktop and Android bumped `2.2.0` → `2.2.1`; repo public-facing version -`4.3.2` → `4.3.3`. - -The apps also catch up with the website: the new Contact page, the reworded -anti-cheat paragraphs of the Disclaimer and the Terms (so they show the -consent gate once, with those paragraphs), and v4.3.2's anti-cheat grouping. -The desktop app offers 2.2.1 through its updater once the release is -published; on Android, install the new APK over the old one. - -### 🔐 Security - -- **Code scanning is clean again.** The worker that decodes the catalogue now - refuses a message from any origin but its own (CodeQL - `js/missing-origin-check`). Only the page that started it can reach it, so - nothing changes for anyone; the alert had been dismissed once and came back - as soon as the code around it moved. -- **CI installs only what it has pinned.** The release workflows, which hold - the signing keys, pin every third-party action to a commit. Every `npm ci` - runs with `--ignore-scripts`, and no workflow uses `npx`. The Python - pipeline pins every package it installs, the dependencies' dependencies - included, with the hash of each file, and installs wheels only - (`--require-hashes --only-binary :all:`), so no package's setup script runs - and nothing unlisted is installed. -- **The Android app no longer takes part in Android's Auto Backup.** Left - unset, Android copied the app's storage (your consent, your settings and - the cached catalogue) into your Google account's backup, while the Privacy - Policy says none of it leaves your device. From 2.2.1 it stays there; on a - new phone you accept the terms again. -- The source no longer contains raw invisible or right-to-left control - characters: the pipeline's lists of characters to strip spell them as - escapes. - -### 🧹 Changed - -- Regexes that could backtrack quadratically on long input are linear now: - the store page's tags and "unsupported" language rows, the discovery - sweep's search rows, the review percentage and label, the chart colour - tokens, the legal pages' titles, the image route's capsule path and a few - more. Each new form was checked against the old one, on the dataset and on - random input. -- Lists sorted for a build hash, the sitemap or a test R2 listing state the - code-unit order they always had; the admin stylesheet puts its `@import`s - first, as CSS requires (the built stylesheet is byte-for-byte the same); - `Number.parseInt` over the global, `[[ ]]` in the bash wrappers; the unused - `normalizeLink` is gone; the Steam client mounts its retrying adapter for - https only. -- New tests pin the store page's tag and language parsing, the discovery - sweep's rows, the review summary parsing and the worker's origin check. - -### 📚 Docs - -- `CLAUDE.md`: the worker's origin check, the CI pinning rules (and how to add - a Python dependency), the Android backup decision. `docs/dev_env.md` and its - Vietnamese copy: run the pipeline from the repo root, with the hashed - installs; they said `cd scripts`, from where `data/` cannot be found. - `docs/DEPLOYMENT.md`: what CI checks, CodeQL and SonarCloud included. - -## [v4.3.2] – 2026-10-16 (The "Pigeonhole" Edition) - -The anti-cheat charts and filters know the products Steam's declarations -brought in. Only the website's anti-cheat grouping and the pipeline's labels -changed: the desktop and Android apps stay at `2.2.0`, with no new build, and -group these products from their next release. Repo public-facing version -`4.3.1` → `4.3.2`. - -### ✨ Added - -- **Seven more anti-cheat families**: ACE (Anti-Cheat Expert), Anti-Cheat - Toolkit, CrackProof, HoYoKProtect, NGS (Nexon Game Security), EA Javelin and - SARD. After v4.3.1, 68 of the 159 games with a named anti-cheat sat in the - charts' "Other" slice; now 35 do, and those are one-off names a developer - typed. New games get the short name as their label; a label already stored - stays as it was written, so nothing in the catalogue is rewritten. - -### 🐛 Fixed - -- A product name now has to appear as a whole word to count. Matching inside - words would have filed "Space Guard", "Interface Shield" or "Peacekeeper" - under ACE, and "Vacuum Protect" under VAC. - -## [v4.3.1] – 2026-10-16 (The "Fair Play" Edition) - -Anti-cheat information comes from Steam again, for every game, and the -retired browser extension leaves the repository. Only the data pipeline, the -admin, the docs and two legal documents changed: the desktop and Android apps -stay at `2.2.0`, with no new build. Repo public-facing version `4.3.0` → -`4.3.1`. - -The data catches up through the pipeline itself. The first data job after -this release cleans the notes once (about 520 games). The first anti-cheat -sweep fills and corrects every game Steam has a declaration for, and every -daily sweep after it keeps them in step. - -### 🐛 Fixed - -- **No game added since September had an anti-cheat.** The browser extension - was the only part of the project that read the anti-cheat a developer - declares on Steam, and it stopped in June; the pipeline itself only looked - for VAC. None of the 4,700 games added since then had one, Delta Force's - kernel-level ACE included. The pipeline now reads Steam's own declaration: - the product, whether it runs in the kernel, and whether it needs Secure - Boot. It does so when a game is added, and for the whole catalogue every - day. More than 80 games that declare an anti-cheat on Steam had none here, - among them Brawlhalla, Destiny 2, THE FINALS, Delta Force, Albion Online, - SMITE 2, Throne and Liberty and Dark and Darker; about 20 more get the - kernel flag or note they were missing. A developer who types a paragraph - where the product name goes gets a label cut to 40 characters, with the - whole text kept in the note. -- **Where the list and Steam disagree, Steam's declaration wins.** Wuthering - Waves uses ACE, not EAC; Jujutsu Kaisen Phantom Parade's anti-cheat does not - run in the kernel; Marvel Rivals' kernel flag is now known. A correction - made in the admin still beats Steam. A game that declares nothing on Steam - keeps what it has, because no declaration is not proof that a game has no - anti-cheat (Warframe, Overwatch 2 and NARAKA declare none). -- A game whose anti-cheat had been reset to an empty value had only its first - Steam category checked for VAC, and a full re-fetch reset `-` to an empty - value. - -### ✨ Added - -- **The anti-cheat sweep** (`scripts/refresh_anticheat.py`), at the end of the - daily Refresh Store Data run, with a commit of its own. About 160 requests - to Steam's store API cover every game; a store page is read only for a - declaration whose name the API leaves out. A manual Refresh Store Data run - with `only: anticheat` runs just the sweep. - -### 🧹 Changed - -- **The browser extension is archived** - ([steam-f2p-extension](https://github.com/poli0981/steam-f2p-extension); - v2.8.0 was its last release). The ingest queue (`scripts/temp_info.jsonl`) - now takes store links only: any other key on a line is ignored, and the game - is fetched from Steam. The code that merged the extension's fields is gone, - along with the field lists that existed only for it. -- The notes the extension left behind are removed: "Has paid DLC" at the - start of 491 notes (the paid-DLC flag already says it, and 10 of those notes - contradicted the flag) and "[hover-add]" on 26. A note left with nothing - else reads "Not reviewed yet". -- DISCLAIMER section 5 and Terms of Use item 5 now say where anti-cheat comes - from: the developer's declaration on Steam. On the website the consent - screen shows those two changes once. -- "Denuvo", Steam's name for Denuvo Anti-Cheat, is grouped with it in the - charts and filters. - -### 🧰 Pipeline - -- Refresh Store Data checks out the tip of `main` when it starts, as the - ingest does, so a run that waited its turn works on current data. -- A retired override whose old value equals its new one no longer counts as a - change on every save. - -### 📚 Docs - -- README, CONTRIBUTING and the contact page no longer send anyone to the - extension. A missing game or a correction goes in Discussions › Ideas, and - the manual fork path queues links only. - -## [v4.3.0] – 2026-10-13 (The "Autopilot" Edition) - -The admin can now approve the review queue on its own, a batch at a time and -within a daily limit, and it can take games out of the catalogue and put them -back. Four new admin pages show what is going on. Only the admin, its Worker -routes and the data pipeline changed: the desktop and Android apps stay at -`2.2.0` with no new build, there is no D1 migration, and the GitHub App keeps -the same permissions. Repo public-facing version `4.2.1` → `4.3.0`. - -Auto-approve is **off** until it is turned on at `/admin/automation`. - -### ✨ Added - -- **Auto-approve.** Every 15 minutes the Worker's cron can approve one batch - of pending games, exactly as a reviewer's Approve does: a request in - `scripts/temp_info.jsonl` that the ingest still checks game by game (free, - reachable, a game, not already listed). The page sets the limits: games per - batch (up to 100), games per day (up to 500, a ceiling written in code), a - minimum wait before a game can be taken, the order, and which discovery - sources. A batch is committed only when the previous one has been ingested - and no data job is running or waiting its turn, since pushing then would - cancel that job. Anything it cannot check counts as "not now". **Run one - batch now** does one on demand, within the same limits. -- **Removing games.** `/admin/remove` takes up to 100 games out of the - catalogue at once, with a reason from a fixed list and an optional note. - Both are public. A removal is a line in the new `data/blocklist.jsonl`, and - every pipeline write leaves those games out. No scrape, re-fetch or - browser-extension push can bring one back, and discovery never proposes it - again. Each removal is logged once in `scripts/removed_games.jsonl`, so the - game's page says it was removed and why. **Restore** puts a game back in one - commit, and the game is fetched fresh from Steam. `scripts/delete_game.py` - does the same from the command line. It used to be an interactive prompt - that kept no record and did not stop the game from coming back. -- **Overview** at `/admin`, with one card each for the queue, auto-approve's - day, removals waiting for the pipeline, data jobs running now, data-quality - totals, and commit jobs that failed or are stuck. The queue moved to `/admin/queue`, and old - links are forwarded there. -- **Pipeline** (`/admin/pipeline`): the latest runs of every data workflow, and - what is running or waiting. -- **Data quality** (`/admin/quality`): published games with something missing - or unreviewed, such as safety never set or never reviewed, no genre, no tags - or no publisher. Each game links to its Edit page. - -### 🐛 Fixed - -- **A free DLC, demo or tool could be added as a game.** The ingest now - refuses anything Steam does not call a game, and logs it as `not_a_game`. - This applies to the browser extension too. -- `ingest_new.py` crashed on an entry whose link was a number, and would have - crashed again on every three-hourly run until the file was cleaned by hand. - A number is now read as an appid, and anything else unusable is counted as - a bad entry. -- An ingest run that waited behind a long data job worked on the data as it - was when the run was queued. It now starts from the tip of `main`. -- `Mark Dead Games` pushed with a bare `git push`, so a commit landing during - its run threw the run away. It now commits through the same - rebase-and-retry helper as every other data job. - -### 🧰 Pipeline - -- `scripts/remove_games.py` applies the blocklist. `Ingest New Game Links` - runs it before every ingest, and a push to `data/blocklist.jsonl` starts that - workflow. A save that would remove more than 500 games stops before writing - anything, so a damaged file fails loudly instead of emptying the catalogue. - `Check Overrides` validates the blocklist on every push that touches it. -- Discovery counts removed games as already known. - -### 🔐 Security - -- The app shell's lockfile takes `rustls` 0.23.45 (and `rustls-webpki` - 0.103.15), closing GHSA-2mjx-qc3c-rqvc: TLS 1.3 handshake messages were - accepted across encryption-level boundaries. Only the desktop updater's - HTTPS client uses it; the Android app does not include it. The desktop app - picks it up in its next build, and 2.2.0 is unchanged. - -### 🧹 Housekeeping - -- 25 merged branches on GitHub, their local copies and 7 stale worktrees are - gone. GitHub now deletes a pull request's branch when it is merged. -- Dependencies: Tauri 2.12.2 and its plugins (#181), and eleven npm - minor/patch updates including Svelte 5.57.2, Vite 8.3.4 and wrangler - 4.149.0 (#182). The website already runs them; the apps pick them up in - their next build. Dependabot no longer proposes SvelteKit 3, - adapter-static 4, a new Svelte, Tailwind or TypeScript major, or a - `@types/node` ahead of the Node 24 the project runs on. - -## [v4.2.1] – 2026-10-10 (The "Age Gate" Edition) - -Adult Only games now have their tags, languages and paid-DLC flag. Every -release date reads the same way, and the catalogue's text no longer carries -HTML escapes, invisible characters or Vietnamese notes. Only the data -pipeline changed: the web app and the desktop/Android apps stay at `2.2.0`, -with no new build. Repo public-facing version `4.2.0` → `4.2.1`. - -The fixes reach the catalogue through the pipeline itself. The next data job -rewrites the dates, notes and text once. The next `Refresh Store Data` run -fills the games that were empty. Every app, old or new, picks the changes up -with its next catalogue download. - -### 🐛 Fixed - -- **Adult Only games had no tags, no languages and the wrong paid-DLC flag.** - Steam answers an anonymous visit to such a game's store page with its age - check, a Sign In page no cookie gets past, and the pipeline read that page - as the game's own: no language table, no tags, no DLC section. 25 games - were stuck that way: about 16 adult games, plus Warframe, PUBG, Rainbow Six - Siege and other age-rated games that were gated on the US servers the - pipeline runs on. Every one of them was marked "no paid DLC". A gated page - is now recognised and never read. Those games come from Steam's own store - data instead: tags, languages with their interface/audio/subtitle columns, - and the paid-DLC flag from the prices of their DLC. A game with empty tags - or languages is retried every day until they fill. -- **"Point & Click".** 458 games had the tag written out with its HTML - escape, next to 10 with "Point & Click", so the tag filter listed both - (also "Design & Illustration" and "Animation & Modeling"). About 320 - descriptions showed `"` instead of quotation marks. -- TrackMania Nations Forever listed a language called "#lang_slovakian"; it - is Slovak. - -### 🧹 Changed - -- **One release-date format.** Every release date reads like "Aug 21, 2012". - The catalogue held three shapes: about 1,360 games in "21 Aug, 2012" and - one in Russian. Dates sent in another order or another store language are - converted when they are saved. Placeholders such as "Coming soon" are left - as they are. -- The note "Có DLC trả phí", which the browser extension wrote on 482 games, - now reads "Has paid DLC". -- Invisible characters (zero-width spaces, stray direction marks) and stray - spaces or tabs are removed from 56 games' names, developers, publishers and - descriptions. Two games listed a publisher that was only a space. - -## [v4.2.0] – 2026-10-03 (The "All-Time High" Edition) - -Every game now shows the most players it has ever had at once, the catalogue -the site and the apps keep for offline use is a fraction of its old size and -no longer readable as text, and every open dependency alert is closed. Web -app + desktop/Android bumped `2.1.1` → `2.2.0`; repo public-facing version -`4.1.1` → `4.2.0`. - -On the website all of this is already live. The desktop app offers 2.2.0 -through its updater once the release is published; on Android, install the -new APK over the old one. The apps also pick up the Disclaimer's new -paragraph on where player numbers come from, so they show the consent gate -once, with that paragraph; the website already did. - -### ✨ Added - -- **All-time peak players.** Every game shows the most players it has ever had - at once: "All-time peak" on its page, and a sortable column in the games - table and the CSV export. The number is the peak Steam Charts has recorded, - which for a game it tracks goes back to the launch, read about once a month - per game; for the many small games Steam Charts does not track, it is the - most this project's own samples have seen. It only ever goes up. The - "(peak N)" beside the player count is gone: it was the highest of our own - occasional samples since the last full re-fetch, not a daily or all-time - peak, and it read like one. The Disclaimer names the new source, so - returning visitors see the consent gate once, showing that paragraph. - -### 🗜️ A smaller, opaque offline cache - -- **The catalogue your browser or app keeps for offline use is now stored as - the packed shards it downloads**, not as thousands of readable records: - about 1.4 MB instead of roughly 9.5 MB, and opaque bytes in DevTools. - Like the packed downloads, this is compression and obfuscation, not - protection: the key is public, and the dataset stays readable in Git. The - copy an earlier version saved keeps working until the data next changes, - then it is replaced and deleted. Same storage keys, so the Privacy Policy - and the consent gate are unchanged. -- Opening the cached catalogue happens off the main thread now: on a - desktop the longest freeze while loading it fell from about 20 ms to 6 ms, - for about 45 ms more until the data is ready. The two cache keys are now - written in one transaction, so a failed write can no longer leave a new - index next to old data, and a cache that will not open is simply - downloaded again. - -### 🧰 Pipeline - -- `scripts/refresh_peaks.py` and the daily "Refresh All-Time Peaks" workflow - (19:30 UTC) ask Steam Charts about a thirtieth of the catalogue a day, a - page every two to three seconds, and stop for the day if it ever refuses; - every run also raises the field from the pipeline's own player counts. A - manual run with `backfill` ticked asks about every game at once, in about - four hours. - -### 🔐 Security - -- **Every open dependency alert is closed** (19 from Dependabot, plus the few - `npm audit` adds); `npm audit` reports none. Only two of the packages run in - production: `devalue`, whose parser is in the page and the apps (5.9.2 → - 5.9.4), and `urllib3` in the data pipeline (2.7.0 → 2.8.0). The rest are - build and development tools: `undici` comes up to 7.29.1 with wrangler - 4.147.0, and `brace-expansion`, `fast-uri` and `serialize-javascript` are - lockfile-only bumps. SvelteKit 2 still asks for `cookie` 0.6, whose fix is - only in SvelteKit 3, so an npm override gives it 0.7.2 (same API; with the - static adapter that code only runs while the site is built). The `sharp` - override is gone: wrangler's own pin now holds the patched version. - -## [v4.1.1] – 2026-10-03 (The "Pocket-Sized" Edition) - -The site and the apps fit a phone: nothing runs off the right edge, game -names are back in the leaderboards, and the Android app no longer puts its -top bar under the clock. Web app + desktop/Android bumped `2.1.0` → -`2.1.1`; repo public-facing version `4.1.0` → `4.1.1`. - -On the website the phone fixes go live with this release; the caching -changes below already were. The desktop app offers 2.1.1 through its updater -once the release is published; on Android, install the new APK over the old -one. The apps also pick up the Privacy Policy line about the image host -below, so they show the consent gate once, with that paragraph; the website -already did. - -### 📱 Fits a phone - -- **Nothing runs off the right edge any more.** On a phone, the Dashboard's - "Top genres", "Playing right now" and chart cards, and every card on - Developers and Publishers, were wider than the screen: the counts and the - "View all" links were cut off and the page slid sideways. One long name was - enough, because a grid with no column count for small screens grows to fit - its longest line. Every grid now starts at one column that fits the screen, - and a test fails on any grid that does not. -- **Game names are back in the leaderboards.** Top Online, Top Offline and the - developer and publisher pages squeezed the name to nothing to make room for - the genre badge and the review score. On a phone those two now give way to - the name. -- **The Android app keeps out from under the status bar.** Since 2.0.0 the top - bar sat under the clock and the battery icon: the safe-area padding the 1.x - app had was lost in the rewrite. The page, the menu, the dialogs, the - back-to-top button and the notifications clear the status and navigation - bars again, and a strip behind the status bar keeps the clock readable - whichever theme the app and the phone are in. This needs Android System - WebView 136 or newer, which any phone that updates it from the Play Store - has. -- **Charts that fit.** On a phone the Anti-Cheat, Delisted and Catalogue - growth legends no longer cover the chart, axis numbers no longer print on - top of each other, and the tag cloud shows the most common tags instead of - dropping exactly those. -- **Smaller fixes.** The header search shows its hint instead of "Search by - na"; on /games a game with a long anti-cheat name no longer paints over the - next card; the consent gate scrolls to its top on a short screen; long - names and links in titles and game descriptions wrap instead of widening - the page. - -### ⚡ Faster repeat visits - -- **Static files are cached by what they are.** Only the hashed scripts, - styles and fonts had a lifetime; the icons, the favicon, the social card, - the manifest and Workbox's runtime were asked for again on every page load. - Workbox's hashed runtime is now cached for a year like the rest of the - build, and the art and manifest are fresh for a day and then refreshed in - the background. Pages, the service worker and the version signal still - revalidate every time, so a deploy - or a changed legal document - shows - on the next load. -- **Game art comes straight out of Cloudflare's cache.** Every thumbnail and - hero ran the site's Worker on every view, however often it had been seen - - a Worker always runs before the cache. The website now loads the AVIF - copies from the site's own image host, `media.free-steam-games.win`, which - Cloudflare caches like any static file, and falls back to the old address - by itself for art the cron has not converted yet or a browser without AVIF. - The desktop and Android apps are unchanged. The Privacy Policy now names the - image host, so returning visitors see the consent gate once, showing that - paragraph. - -### 📚 Docs - -- `docs/DEPLOYMENT.md` explains which commits deploy: documentation commits - stopped deploying, data commits still did, and it gives a configuration that - stops both - with the one trap: the legal documents are read by the build, - so a commit that changes only them must still trigger one. -- `docs/android-support.md` (and its Vietnamese mirror) says which Android - System WebView the safe areas need, and what to do on an older one. - -## [v4.1.0] – 2026-10-02 (The "Featherweight" Edition) - -Game art and the catalogue both got much lighter, the deploy log lost its -noise, and scrollbars finally look like the rest of the site. Web app + -desktop/Android bumped `2.0.2` → `2.1.0`; repo public-facing version `4.0.2` → -`4.1.0`. - -The web changes are already live. The desktop app offers 2.1.0 through its -updater once the release is published, and brings the packed catalogue with -it; on Android, install the new APK over the old one. Returning visitors see -the consent gate once, showing one new line in the Privacy Policy: the storage -key of the new scrollbar setting. - -### ✨ Added - -- **Game art is AVIF now - heroes about 58% smaller, thumbnails about 92%.** - The Worker's 15-minute cron encodes each game's Steam header once with - Cloudflare Images - a 230 px thumbnail and a 460 px hero - and stores it in - R2; every request after that is served from the stored copy, never encoded - on the fly. The ten most-played heroes went from 40 KB to 16.8 KB (SSIM - 0.979 against Steam's JPEG); thumbnails are ~3.4 KB. Most-played games go - first, the whole catalogue takes about a day and a half, and a hard monthly - cap keeps the Images bill bounded. Browsers that do not take AVIF keep - getting Steam's JPEG, and social cards always do. -- **The catalogue downloads in about a seventh of the bytes.** The app now - reads each shard as a packed file (`/api/data/p1/*.bin`, 224 KB instead of - 1.5 MB): compressed, and wrapped so the site's API is no longer a - ready-made JSON feed. It is obfuscation, not secrecy - the readable dataset - is the repository, as it always was. The app checks what it unpacks against - `index.json` exactly as before, and the released apps keep reading the - plain files. -- **Scrollbars match the site, and can be hidden.** A warm thumb that turns - amber under the pointer, in both themes. Settings → Scrollbars: Visible, - Hidden in tables and panels, or Hidden everywhere; hidden bars still scroll - with the wheel, trackpad, touch or keyboard. - -### 🐛 Fixed - -- **Every deploy log was 91% noise.** The build printed one - `[404] GET /img/…` per prerendered game - 5,566 lines - and rendered an - error page for each. They were harmless (a Worker route the build cannot - see), but they buried anything worth reading. Now there are none. -- **The plain catalogue went out uncompressed.** Cloudflare does not compress - `application/x-ndjson` by default, so every full load moved ~9 MiB. A - Compression Rule now brotli-compresses those files for every client, - released apps included (1.5 MB → 226 KB per shard). -- **Tables showed the operating system's grey scrollbar.** Tailwind 4.3's own - `scrollbar-thin` merged with ours and, in Chromium, switched the themed bar - off. Ours is now `scrollbar-slim`, with a test that keeps it that way. -- **Thumbnails cost two guaranteed 404s on half the catalogue**, probing for a - Steam capsule that hashed paths never have, and stray query strings forked - the image edge cache. -- **A data-only commit redeployed the whole site** (5,681 files), against - what `docs/DEPLOYMENT.md` intends. The fix is the Workers Builds watch - paths, a dashboard setting. - -### 🔐 Security - -- **`/img/*` can no longer be used to run up the image bill.** With - Cloudflare's URL transformations enabled, `/cdn-cgi/image//img/…` - let anyone bill a new transformation per option set, through a proxy that - serves any Steam game's art - a scanner found such a URL within minutes. The - Worker now refuses the transformation service as a client, and URL - transformations are switched off for the zone; the cron's encoding does not - need them. - -## [v4.0.2] – 2026-09-29 (The "Right Address" Edition) - -A game's tags, languages and store details are now re-read on a rotation -instead of being fetched once and never again, a long data job no longer loses -its work when something else lands on `main`, and each kind of message now has -an address of its own. Web app + desktop/Android bumped `2.0.1` → `2.0.2`; repo -public-facing version `4.0.1` → `4.0.2`. - -The web changes are live as soon as this merges. The desktop app offers 2.0.2 -through its updater once the release is published; on Android, install the new -APK over the old one. Returning visitors see the consent gate once, listing -the Privacy Policy, the Terms of Use and the Data Licence — each changed only -by a contact address, and the gate shows exactly that line. - -### ✨ Added - -- **Tags, languages and the rest of a game's store data now stay current.** - `update_data.py` only fills in incomplete records, and only empty fields, so - once a game had its tags, languages, platforms or header image nothing looked - at them again short of a manual full re-fetch. `Refresh Store Data` (daily, - 16:00 UTC) re-reads them on a rotation: the store page - tags, languages and - their details, the paid-DLC flag - for every game once a week, and - appdetails - name, header image, description, developer and publisher, - release date, platforms, Metacritic, DRM notes - once a month. About 630 - store pages and 150 appdetails calls a day instead of 8,800 requests in one - sitting. It never blanks a value on a failed or age-gated page, never - touches the hand-set fields (genre, type, anti-cheat, safety, notes), and - marks a game updated only when something changed. A dry run on three games - found all three with tags that had drifted since they were first fetched. - -### 🐛 Fixed - -- **A long data job lost its work if anything landed on `main` meanwhile.** - `purge-unhealthy` ran for four hours on 2026-09-21 and then failed on - `push rejected (fetch first)`: the data-write group serialises workflows, - but a merged pull request or an `/admin` commit still moves `main`. Every - data job now commits through `bash/commit_push.sh`, which rebases onto - `origin/main` and retries the push. - -### 📇 Contact - -`contact@poli0981.dev` stays the default. Three role addresses join it, each -published where a reader of that document would look: - -| Address | For | Where | +| Version | Date | Edition | |---|---|---| -| `security@poli0981.dev` | vulnerabilities, after GitHub's private reporting | `SECURITY.md`, `/.well-known/security.txt` | -| `privacy@poli0981.dev` | privacy questions | Privacy Policy | -| `copyright@poli0981.dev` | copyright, DMCA and takedown notices | Data Licence, Terms of Use §6 | - -The maintainer's website, , is on the About page next -to the email and the links page. `security.txt` now lists GitHub's private -vulnerability reporting first and `security@` second, in RFC 9116 preference -order. The full map is in `AUTHORS.md` and `docs/Contact.md`. - -## [v4.0.1] – 2026-09-23 (The "Human Check" Edition) - -The web app now asks each browser to pass a Cloudflare Turnstile check once a -day after the terms are accepted, shows a changed legal document as a diff -instead of asking for a full re-read, and counts page views with Cloudflare -Web Analytics. The desktop app's game artwork - blank because its webview -sends a Referer the zone's Hotlink Protection refuses - is back, and nothing in -the app loads data before the reader is past the consent step and the check. Web app + desktop/Android -bumped `2.0.0` → `2.0.1`; repo public-facing version `4.0.0` → `4.0.1`. - -The web changes are already live - pushing `main` deploys. The desktop app -offers 2.0.1 through its updater once the release is published; on Android, -install the new APK over the old one. Returning visitors see the consent gate -once, listing only the Privacy Policy and Terms of Use changes. - -### ✨ Added - -- **A legal document that changes now shows you the change, not the whole - document again.** Each binding document is hashed at build time - (`virtual:legal-versions`); when one differs from the version you accepted, - the consent gate reopens on its own and lists only that document, with a - `+`/`-` diff against the copy kept in your browser. `TERMS_VERSION` is no - longer the only signal — it stays as the lever that forces a full re-read. - Clearing site data removes the stored copy, and the gate then links to the - full text instead. -- **Cloudflare Web Analytics**, cookieless, loaded only after you accept the - terms and never in the desktop or Android apps. It replaces an "automatic" - edge injection that had been enabled for months and could never have worked: - it inserts an inline script, and a hash-based CSP ignores `'unsafe-inline'` - by specification, so it only ever produced two console errors per page load. - Measured on the live site: the beacon returns 200 and its reports 204, with - nothing loaded at all before consent. -- **A human-verification step for suspicious page loads, and a country block** - (mainland China, Russia, Argentina). Both are WAF custom rules, live since - 2026-09-20 and documented with their expressions and every exclusion in - `docs/SECURITY_SETUP.md`. Verified after they went live: a plain `curl` with - no browser User-Agent is still served every public path, and the challenge - rate has stayed at 0%. `BLOCKED_COUNTRIES` in `wrangler.jsonc` makes the - Worker refuse the same countries as defence in depth; the rule is the - boundary, because prerendered pages never reach the Worker at all. -- **A Cloudflare Turnstile check on the website**, separate from the WAF - challenge above: after accepting the terms, each browser passes a Turnstile - widget at most once every 24 hours before the app loads its data. The Worker - verifies the token at `POST /api/human-check` with the `TURNSTILE_SECRET` - secret, checking the action and the hostname; nothing is stored server-side. - It is an overlay like the consent gate, so prerendered pages and crawlers are - unaffected, and it is soft on purpose: `/api/data/*`, `/img/*` and the - desktop and Android apps never require it (the Terms of Use promise as much). - It refuses only when Cloudflare says no; a missing secret, a siteverify - outage, a widget misconfiguration or being offline let the reader through for - that page load. The web CSP gains `challenges.cloudflare.com` in `script-src` - and a new `frame-src`; `verify-dist.mjs` fails the Tauri build if either - appears there. The privacy policy and the terms describe it, so returning - visitors see those two documents' changes at the consent gate once. - -### 🐛 Fixed - -- **Game artwork was blank in the desktop app** (and would be on Android): the - WebView2 webview sends `Referer: http://tauri.localhost/`, and the zone's - Hotlink Protection refused every `/img/*` request carrying it — before the - Worker ran, so nothing in the app's logs showed it. Every `` now sets - `referrerpolicy="no-referrer"`, which the protection allows, and - `src/lib/images.test.ts` fails on one that does not. That also fixes the - thumbnails `npm run dev` could never show. Installed 2.0.0 apps are covered - by a Configuration Rule on the zone until they update; Hotlink Protection - itself stays on for other sites. -- **`/activity` and `/charts/delisted` fetched their data before consent.** The - root layout held the catalogue back, but those two pages called `load()` - from effects of their own, and the activity feed also refetched on window - focus. The gate now lives in `Resource` itself: an `enabled` option read - inside every `load()`, which every resource sets to `appReady()` - consent - accepted and the human check cleared - so a held-back load starts by itself - once both are passed. `src/lib/resource.test.ts` fails on a `new Resource` - without it. -- **The service worker threw `non-precached-url: /200.html` on every page - load.** `navigateFallback` named the adapter-static fallback, which is - written into `dist/` after workbox has already globbed the build output — so - it was never in the precache, and the throw abandoned the rest of the - worker's setup. It is now `/`, which is both precached and what Cloudflare - and Tauri already serve for an unmatched path. `verify-dist.mjs` fails the - build if the two ever disagree again. -- **`/admin` no longer writes the maintainer's email address into public Git.** - Commit bodies and `data/overrides/*.json` say `admin`; the four override - files that already carried it were rewritten. The acting identity is still - recorded in D1, where `/admin/audit` reads it. - -- **`/admin` said "Your Cloudflare Access session has expired" straight after - signing in, in a private window too.** Its API was at `/api/admin/*`, behind - a second Cloudflare Access application. Access issues its session cookie per - application and `fetch()` cannot follow the sign-in redirect, so the session - for `/admin` never reached the API and every call bounced to the login page. - The API now lives at `/admin/api/*`, under the page's own application, and - `worker/index.test.ts` drives it through the real router and token check. - The `/api/admin` Access application is no longer used and can be deleted. -- `scripts/discover_new.py` took any host ending in `cloudflareaccess.com` for - an Access login page, lookalikes included; the suffix check now needs the dot. -- The i18n, SEO and chart tests share one comment stripper instead of three - regexes, one of which removed text that was never inside a comment. - -### 📚 Docs - -- `docs/ACKNOWLEDGEMENTs.md` listed the dependencies of the **React** app — - React 18, react-router, i18next, Zustand, TanStack Query, Radix, shadcn/ui, - OpenPGP.js, Tailwind 3, TypeScript 5, PostCSS. None of that has shipped since - the v4 rewrite. Replaced with the real list, licences checked against - `node_modules` rather than remembered (`echarts-wordcloud` is ISC, not - BSD-3-Clause), and the claim that `/about` carries a "full SPDX list" dropped - — it is a curated subset. -- `docs/DEPLOYMENT.md` records that a zero-duration "Workers Builds" failure on - a PR branch is a preview-build artefact, not a broken commit, so the next - person does not go looking for a bug that is not there. -- `docs/SECURITY_SETUP.md` section 10 claimed the packaged apps survived Hotlink - Protection because their webview sent no Referer, recommended switching the - protection off, and said no allowlist could express the apps' origin. The - first was no longer true and the last never was; it now documents the - per-image fix and the Configuration Rule, with the measured check. A new - section 12 covers the Turnstile widget settings, the secret and local testing - with Cloudflare's test keys (`web/.dev.vars.example`). -- Stale `public/_headers` paths (the file has been `static/_headers` since the - SvelteKit move) and a `SITE_ORIGIN` that is really `API_ORIGIN` in - `src/lib/site.ts` are corrected in `worker/lib/http.ts`, `svelte.config.js` - and the security doc; `_headers` itself gains comments on why images opt out - of its Referrer-Policy. - -### 🛠 CI - -- The Android release builds the tag it releases (a manual run used to build - `main`), installs `platform-tools` only (the SDK no longer carries `tools`, - which stopped `android-v2.0.0`), and names the commit it built. -- CodeQL also runs when only `.mjs`/`.cjs` files change, and - `verify-dist.mjs` finds `