The first release in maintenance mode, and a security one: the apps take
rustix 1.1.6 (RUSTSEC-2026-0486, reachable through the updater's tar and
xattr code), the About page's data-only report links, and two weeks of
dependency updates; the repository gains Qodana with its first findings
fixed.
Version bumps: web/package.json and its lock, src-tauri/Cargo.toml and the
f2p-tracker entry in Cargo.lock, and tauri.conf.json (Android's versionCode
derives from it).
The first release under the changelog split: [Unreleased] becomes
changelog/v4/4.7.x/4.7.2.md (sub-headings up one level, an intro first,
and the "no release yet" phrases reworded), CHANGELOG.md keeps an empty
[Unreleased] and gains the release's row. The GitHub release's notes are
that file below its title and back link.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42
releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases
(none has been published; its README says how one would be filed).
CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly
as it was, and a table per major version (version, date, edition) that
links each file.
Each file is its section, copied byte for byte except that its heading
is the file's H1 (so the sub-headings move up one level, outside code
fences), relative links gain ../../../ so they name the same repository
paths, and the --- separators between sections are gone. Checked by
reversing all three changes on every file and comparing with the
original section: 40 of 40 equal. Two releases had no section: v1.0.0
(its GitHub release notes, which the changelog pointed to as "Initial
stable") and v1.1.3 (its tag message).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rustix 1.0.0-1.1.5 marks as initialised the bytes an extended-attribute
call (getxattr, listxattr and their l/f forms) never wrote when given a
zero-length buffer - undefined behaviour from safe code. Fixed in 1.1.6
(2026-10-27). In the Tauri shell it comes in through async-io, polling,
zbus and tempfile, and the affected calls through tauri-plugin-updater ->
tar -> xattr. Dependabot raised no alert; an OSV querybatch over
Cargo.lock found it.
Cargo.lock: rustix's version and checksum only. `cargo update -p rustix
--precise 1.1.6` (cargo 1.99) also re-pointed thirteen unrelated
dependency edges to older windows-sys versions and one from syn 3 to
syn 2, so the entry was edited by hand instead; rustix 1.1.6's minimums
(bitflags 2.9.2, errno 0.3.10, libc 0.2.182, windows-sys >=0.52,<0.62)
are all met by what is locked. `cargo metadata --locked` (every platform)
and `cargo test --lib --locked` pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
README: a Qodana badge and the workflow in the list of scanners.
DEPLOYMENT: what qodana.yml runs, the three secrets, the gate, and what
to remove if the licence ends. CLAUDE.md: the setup and the traps the
first runs found (no interpreter in native Python, the Rust image's
missing linker and libraries, plugins only in Docker, the lucide import
false positive). CHANGELOG [Unreleased]: the Qodana entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot's npm-minor-patch group (#256): @lucide/svelte 1.72.0,
bits-ui 2.21.0, knip 6.45.1, rollup-plugin-visualizer 7.1.3, vite 8.3.8,
wrangler 4.162.0 - all released at least four days ago.
#256 failed Web CI on knip: 6.45 follows tsconfig.json's `extends` and
reports "$app" (from "$app/tsconfig", which `svelte-kit sync` generates
into node_modules/$app) as an unlisted dependency - an error. It cannot
be taken back with ignoreDependencies: knip matches those against a
package name, and getPackageNameFromModuleSpecifier() returns nothing for
a specifier starting with "$", so the item is never compared (and "$app"
would be read as a regex anyway). knip.json now ignores unlisted
dependencies in tsconfig.json only (ignoreIssues). The export backlog and
the three configuration hints are unchanged from main.
Local proof: typecheck, 747 tests, build + verify-dist --web (18,911
pages, precache 177 entries, as live), cf:check, knip, Tauri build +
verify-dist --tauri.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The project is stable: no new features, code changes only for security
advisories and runtime/dependency updates, and issues and pull requests
are for the data (add, correct, remove a game).
- README: status, build, quality, version, licence and runtime badges, a
"Project status" section, and a data-first Contribute section
- CONTRIBUTING, SECURITY, Contact, the PR template and CLAUDE.md state
the same policy
- Issue forms: add_game and edit_game are new; feature_request, feedback
and off_topic are removed; blank issues are off (config.yml)
- About page: "Report something" links the five remaining forms
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Dependabot #249 (coverage 7.17.2), #250 (action-gh-release 3.0.4,
sonarqube-scan-action 8.4.1) and #251 (twelve npm patch and minor
releases) were merged as they were. Nothing security-relevant, so the
entry waits in [Unreleased] for the next release.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The apps go from 2.5.0 to 2.5.1, which is the first app build with the
accessibility fixes from #244. The desktop app is also the first build that
can zoom.
Version bumps: web/package.json and its lock, src-tauri/Cargo.toml and the
f2p-tracker entry in Cargo.lock, and tauri.conf.json (Android's versionCode
derives from it).
The CHANGELOG's [Unreleased] section becomes v4.7.1, with an intro, and a
fresh [Unreleased] goes above it. ACCESSIBILITY.md now says what works for
the website and the apps 2.5.1, instead of "the apps get it with their next
release".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
src/lib/a11y.test.ts reads the source, like mobile-layout.test.ts. It
checks:
- the table's roles, counts and row indexes, and that no <a> is a row or
carries a fake link;
- every column has a name, and the cards are a list with positions;
- the panes have a minimum height;
- there is no colour-only kernel badge;
- the overlays are dialogs that focus themselves and make the page inert;
- the palette shortcut stands down, and back-to-top is inert while hidden;
- the zoom setting and its capability are present.
It also computes the theme's contrast with the WCAG formula, so a token
edit that drops below 4.5:1 for text or 3:1 for a control's edge fails.
ACCESSIBILITY.md moves the fixed items from "Known limitations" to "What
works today". The desktop and Android apps 2.5.0 predate them and get them
with their next release. CLAUDE.md lists the rules behind each fix, and
CHANGELOG [Unreleased] describes them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A read-through against the code found about forty claims that had drifted.
README:
- Dynamic game-count and version badges. The count is index.json's total.
The version is the newest v* release by semver, since an app release
published last would otherwise count as "latest".
- SvelteKit 3, every desktop package, and the shard layout without a last
shard number.
- The media host, which commits deploy, and the nine workflows the table
left out.
- The accessibility statement and form in the link lists.
SECURITY.md:
- Fix the broken bullet list.
- Describe the real stack, and pushes with the built-in GITHUB_TOKEN.
- Add to scope: the media host, /api/ingest/*, /api/updates/desktop and the
avatar origin.
AUTHORS.md and username.txt:
- Donations are in FUNDING.yml.
- The Add-games template is gone.
- Test devices come from pc_spec.
The issue forms lose the hash URLs, the GitHub Pages permalink, and the
editing and GPG options.
web/README.md, dev_env (EN + VI), the acknowledgements and the contact page
are updated to match. The last two are not consent documents, so nobody is
asked to accept the terms again.
CHANGELOG [Unreleased] lists all three commits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Desktop and Android 2.4.1 -> 2.5.0 (package.json and its lock,
tauri.conf.json, Cargo.toml, the f2p-tracker entry of Cargo.lock); repo
public-facing version 4.6.1 -> 4.7.0. CHANGELOG: the random games page,
Leave site, Decline quitting the Android app, and the 2026-11-03
dependency pass that waited in [Unreleased]. No legal document changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Takes Dependabot's npm group (#236) and cargo group (#234) together: the
Tauri shell plugin moves to 2.6.0 on both sides, and the CLI refuses a
JavaScript/Rust pair on different minors. Adds the SvelteKit 3.1.1 and
adapter-static 4.0.1 patches (exact pins kept), @types/node 26.6.6, knip
6.44.1 and @lucide/svelte 1.66.0 - everything at least three days old;
newer releases wait for next week's Dependabot run.
wrangler 4.156.0's miniflare pins undici 7.30.1 itself, so the
"miniflare": {"undici": "^7.30.1"} override goes in the same commit, as
CLAUDE.md required. npm audit: only the known deepmerge low advisory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- tauri-plugin-updater 2.14.0 -> 2.14.1 moves its Windows zip reader from
zip 4.6.1 to 9.2.0: closes Dependabot #82 (critical), #83, #84 and
RUSTSEC-2026-0367/0368/0369. Targeted cargo update; cargo test --lib ok.
- npm overrides workbox-build -> glob ^14.0.2 and filelist -> minimatch
^11.0.1 (GHSA-3g3m-2fjr-6pw4, GHSA-g3hv-75wg-m249, published 2026-10-30).
The precache lists the same 172 URLs as before.
- deepmerge (#81, low) has no fixed release: build-time only, dismissed.
- CLAUDE.md: when the new overrides and the undici one can go.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
appdetails writes "Free To Play"; SKIP_GENRE_TAGS said "Free to Play", and
the exact match let 1,357 of 12,854 games be stored with it as their genre
(the third most common), while the fallback to the first name could pick
it as well.
- fetcher.pick_genre() compares casefolded and never falls back to a price
model or a release state (NOT_GENRES); with nothing else it says
"Uncategorized". ingest uses it.
- Refresh Store Data replaces a stored one from appdetails: 150 games a
day, first after the page repairs, never under an override. It is the one
manual-field value the job writes; no person chose it. A dry run on the
first 150 (2026-10-30): Casual 91, Indie 24, Strategy 11, Simulation 11,
Uncategorized 10, three others; all answered, no override.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/plan/19-all-languages.md: what kept them out, what every workflow
does with them, the re-sweep, and what is left.
- CLAUDE.md: discovery's language rules, ASCII appids, search folds but
storage never does, re-cut descriptions are not news.
- docs/ADMIN.md: the filters as they are now, re-sweeping a whole year,
the Languages line in the candidate dialog.
- README.md, docs/plan/11 (the decision changed), CHANGELOG [Unreleased].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Measured on production after v4.5.1 deployed (2026-10-27, SIN): over one
keep-alive connection each budget held exactly - /api/no-such-route
121 x 404 then 429 with Retry-After, no-store and CORS; /api/human-check
19 then 429 - while requests on fresh connections, which Cloudflare
spreads over many servers, were never refused (175 human checks in 70 s
against a budget of 20). A probe Worker in a remote preview confirmed the
binding itself enforces (limit 5: 6 allowed, then refused).
So the layer stops browsers and connection-reusing scripts; a client that
reconnects for every request is the WAF rule's, which counted exactly
(250). The docs, CLAUDE.md, the module comment, wrangler.jsonc and the
unpublished v4.5.1 entry said "per location, approximate"; they now say
what was measured. The section 3b check used xargs (fresh connections) and
would have shown no 429 - it now sends everything over one connection.
No behaviour change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Worker-side rate limits behind the edge rule, and the recommended
site-wide WAF rule. Repo-only: nothing in the apps changed, so desktop and
Android stay at 2.3.0 with no new build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SvelteKit 3 (PR #218) under the site and the apps, plus Tauri 2.12.5 from
Dependabot #214. Desktop and Android 2.2.2 -> 2.3.0 (package.json + lock,
Cargo.toml + the f2p-tracker entry in Cargo.lock, tauri.conf.json);
CHANGELOG section dated, fresh [Unreleased].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The SvelteKit 3 fallback for a /#/ path that matches no route passed the
hash straight to location.replace(): CodeQL code-scanning alert #25,
client-side XSS, and an open redirect in practice - `#//other.example/x`
resolved to another site once goto rejected it.
The hash is now resolved against the page's origin and ignored when it
names another one, goto gets that URL, and an unmatched path goes to the
404 page at its fixed address (/error/404). Nothing from the hash reaches
location.* any more. Tests cover both off-site forms (`#//host`,
`#/\host`) and the 404 fallback; checked in a browser on `npm run dev`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sveltejs/kit 2.70.3 -> 3.1.0, @sveltejs/adapter-static 3.0.10 -> 4.0.0.
Closes GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r (dismissed in v4.4.1
as not applicable), and drops the cookie override kit 2 needed: npm audit
reports nothing.
- Config: svelte.config.js is refused by kit 3. Its options are now
sveltekitConfig(tauri) in build/sveltekit-config.ts, passed by
vite.config.ts as sveltekit(sveltekitConfig(IS_TAURI)), with tests for
both CSP flavours, paths.relative, the sitemap entry and the prerender
404 handler. The unused, now-deprecated "@" alias and typescript.config
hook are gone; tsconfig.json extends $app/tsconfig and owns `include`.
- $lib -> #lib (package.json imports), with .js on module imports.
tsconfig repeats the mapping in `paths`: svelte-check --tsgo only maps
.svelte imports through `paths`, and without it every #lib component
fell back to the *.svelte shim (props unchecked; proven with a planted
error).
- Param matchers: src/params/legaldoc.ts -> src/params.ts (defineParams).
vite build imports that file with Node's own import(), so it imports
#lib/legal.ts and legal.ts imports ./schema.ts by their real names.
- PWA: @vite-pwa/sveltekit never supported kit 3 and wrote the worker when
the SERVER build closed, which kit 3's environment build does first.
build/pwa.ts wires vite-plugin-pwa in a buildApp hook after kit's
prerender and before its adapter, with the same globs and URL mapping.
- goto options renamed (replace, reset: false, refreshAll); the /games
filter write is a shallow goto; a legacy /#/ path that matches no route
falls back to location.replace (kit 3's goto rejects it). Hook types
from @sveltejs/kit/hooks; the client handleError returns nothing to keep
kit's message.
- runed 0.35 (bits-ui) peers kit ^2: overridden to our kit, as for
echarts-wordcloud.
Verified against a kit 2 build of the same commit: same 11,037 files bar
hashed chunks, same non-immutable precache URLs, navigateFallback "/",
identical CSP per page (hashes masked), manifest and sitemap byte-equal,
same visible text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Desktop and Android 2.2.1 -> 2.2.2 (package.json + lock, Cargo.toml + the
f2p-tracker entry in Cargo.lock, tauri.conf.json), so the apps ship the
patched rustls/webpki stack their updater uses. CHANGELOG section dated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first run of the new Update Reviews on main asked appreviews about the
12 games GetItems counted at 0, and all 12 failed: since 2026-10-23
store.steampowered.com/appreviews/<id>?json=1 answers 302 to the store
front, from GitHub's runners as from anywhere else (it worked on 10-17).
The 38 games the ingest added that day were listed with "N/A".
- fetch_full() falls back to the GetItems summary when appreviews gives
none (reviews_from_store_api()), so an ingest gets the value the daily
refresh would write.
- update_reviews: a game never read ("N/A", nothing) with a count of 0
becomes "No reviews" without a question; the first count GetItems has
replaces it. A stored percentage is still never replaced by a 0 without a
second source.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/plan/18-pipeline-scale.md holds the measurements (9,847 games,
+~280 a day), what each job cost, what GetItems answers, the direction
and what is left. CLAUDE.md gains the rules for reviews, the purge,
budgets and the data-write group; README the new schedules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scan job now runs both suites with coverage before scanning:
pytest --cov (pyproject.toml: scripts/ without its tests, relative
paths, coverage.xml) and `npm run test:coverage` (vite.config.ts: v8,
lcov with projectRoot "..", so paths start web/). sonar-project.properties
names both reports and drops sonar.coverage.exclusions.
requirements-test.txt gains pytest-cov 7.1.0 and coverage 7.16.2 with
every file's hash (uv pip compile --universal --generate-hashes
--python-version 3.15; the existing pins are unchanged). web gains
@vitest/coverage-v8 5.0.5, matching vitest; none of its packages has an
install script. Coverage stays off for a plain `npm test`.
The token check is its own job, so the scan steps no longer each repeat
the condition; the workflow grants nothing at the top and the scan job
contents: read. `npm run build:admin` replaces the bare `svelte-kit
sync`: it syncs too, and writes the admin bundle the Worker's tests load.
Locally: 576 vitest tests at 58.35% of lines, 299 pytest tests at 57.7%.
Against main's new-code lines (SonarCloud's isNew), the reports cover
92 of 114 coverable lines, 80.7%: the 80% gate is borderline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first full CI analysis of main (db804e27) failed the "Sonar way"
quality gate on one condition: coverage on new code 0.0% < 80%, over 109
new lines. The scan uploads no test report, so every executable line
counted as uncovered; automatic analysis never computed coverage, so the
condition was never evaluated before. Every other condition passed, with
0 open issues and 0 hotspots.
sonar.coverage.exclusions=**/* restores that: no lines to cover, no
coverage condition. Measuring coverage means generating reports in the
workflow and removing this line in the same change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A sonarcloud.yml workflow runs SonarSource/sonarqube-scan-action (pinned to
the v8.3.0 commit) on pull requests and main, with full history for blame.
Commits that touch only what the data jobs write are skipped, and a run
without SONAR_TOKEN (forks, Dependabot) passes without scanning.
.sonarcloud.properties becomes sonar-project.properties, now naming the
organization and project key; its scope settings are unchanged. The
toolchain test, Web CI's paths, CLAUDE.md and docs follow the rename.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/plan/16-toolchain-2026.md: the assessment - what each release
changes, what was measured here, the decisions, how to move each runtime
next time, and what was left.
- docs/plan/17-typescript-7.1.md: the springboard for dropping TypeScript 6
once 7.1 ships - start conditions and how to check them, the steps, the
planted-error table and the baselines to compare against.
- CLAUDE.md: "TypeScript is two packages, on purpose" and "One version of
each runtime"; the uv compile line says 3.15.
- dev_env (EN/VI), README, AUTHORS, TAURI.md, web/README, THIRD_PARTY,
DEPLOYMENT (Workers Builds' NODE_VERSION=26, the Checks paragraph),
ACKNOWLEDGEMENTs and the About page's stack list ("TypeScript 7 + 6").
- CHANGELOG: the Tooling entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eMudhra's `emSign ECC Root CA - G3` had intermediates whose private keys
were compromised. certifi 2026.10.18, the version pinned here, had already
removed every emSign root; 2026.10.19 restores the three that are not
affected (G1, C1, ECC C3) and keeps G3 out. The advisory's range still
covered 2026.10.18, so pip-audit flagged it. The hashes come from
`uv pip compile`, one per file on PyPI (wheel and sdist); every other pin
is unchanged.
Checked on Python 3.15.1: --require-hashes --only-binary :all: installs,
the 299 tests pass, pip-audit finds no known vulnerability.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.sonarcloud.properties tells SonarCloud what is code, what is test code and
what to skip. Both start at the root and are split by patterns:
- tests: scripts/tests, every *.test.ts, and what only tests and the admin's
dev server use (lib/testing, worker/testing, admin/mock) - analysed with
the test rules, out of duplication and coverage;
- not analysed: the dataset and pipeline-written files (data/, games/,
*.jsonl), the D1 migrations (SQLite, which the PL/SQL analyser parsed as
Oracle), web/src/app.html (SvelteKit's template; its <title> arrives via
%sveltekit.head%), and what the Tauri CLI generated and nobody edits
(Android res/, buildSrc/, the icon set). The manifest, Gradle build files
and MainActivity.kt stay in.
Simulated on the tracked files: 219 code, 84 tests, 16 excluded, none
indexed twice. Takes effect once on main. Also an [Unreleased] CHANGELOG
entry for this and the updater-json job, and the rule in CLAUDE.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The previous commit said SonarCloud's automatic analysis covers main only.
That was read from an empty pull-request list at a moment when no PR was
open; this PR got its own "SonarCloud Code Analysis" check (quality gate
passed, no new issues). DEPLOYMENT.md and the CHANGELOG entry now say that
CodeQL and SonarCloud both check pull requests and main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Repo public-facing version 4.3.2 -> 4.3.3; web app + desktop/Android
2.2.0 -> 2.2.1 (package.json and its lock, Cargo.toml and the f2p-tracker
entry of Cargo.lock, tauri.conf.json). The apps also pick up the Contact
page, the reworded anti-cheat paragraphs of the Disclaimer and the Terms
(consent gate shown once) and v4.3.2's anti-cheat grouping.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot alert #69: rustls before 0.23.45 accepted TLS 1.3 handshake
messages across encryption-level boundaries. Lockfile only - rustls
0.23.40 -> 0.23.45, rustls-webpki 0.103.13 -> 0.103.15 - and only the
desktop updater's reqwest uses it. cargo test --lib --locked passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Auto-approve for the review queue (off by default, at most 500 a day),
removing games through data/blocklist.jsonl with Restore, and the
Overview, Pipeline and Data quality admin pages. Apps stay at 2.2.0; no D1
migration; the GitHub App's permissions are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pipeline only: nothing under web/ changed, so there is no new web, desktop
or Android build and no app version bump. The catalogue picks the fixes up
from the next data job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An 'Adult Only' game's store page sends an anonymous client to /agecheck/
and on to a Sign In page that no age cookie opens (measured 2026-10-10).
The scraper read that page as the game's own: no language table, no tags,
no DLC section. 25 games sat with empty tags and languages (about 16 adult
games, plus Warframe, PUBG, Rainbow Six Siege and other M-rated games that
were gated on the US runners), and every one was written has_paid_dlc=false.
- steam_client: classify where a store-page request ENDED (the whole
redirect chain), send age cookies with store-page requests only, ask
appdetails and the page for l=english, add GetItems and GetTagList
(keyless).
- store_items: a pure parser for GetItems items in scrape_store_page()'s
shape (ELanguage tables derived from Steam's own data), plus DLC prices.
- fetcher.scrape_store_fields(): the page first, the JSON API when the page
is gated or redirected, has_paid_dlc from the DLC's prices; None never
overwrites a stored flag.
- refresh_store_data: a game with empty store fields is refreshed every
day, first, capped at 150; --missing-only; values compared as stored.
- scraper: unescape tag and language names ("Point & Click"), name the
"#lang_slovakian" token.
- normalize, run by save_main() before overrides (idempotent, never bumps
last_updated): release_date as "Aug 21, 2012" from any shape Steam
writes; invisible characters and stray whitespace out of names and
blurbs; HTML entities decoded in tags and descriptions; the extension's
"Có DLC trả phí" notes as "Has paid DLC" (overrides translated too, so
they cannot flip-flop).
Dry run on the 25 against Steam: 24 filled, 7 has_paid_dlc corrected
(396420 has no languages on Steam itself). The dataset normalised in
memory: 1,360 dates, 482 notes, 781 entity and 56 text records change, a
second pass changes nothing, and no last_updated moves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web app and desktop/Android 2.1.1 -> 2.2.0 (package.json + lock, Cargo.toml
+ the f2p-tracker entry in Cargo.lock, tauri.conf.json, from which the
Android versionCode derives); repo public-facing version 4.1.1 -> 4.2.0.
CHANGELOG's Unreleased section is dated and named, and a fresh empty one
opened above it.
What 2.2.0 brings to the apps: the all-time peak row and column (#167),
the offline catalogue kept as opaque packs (#169), and the dependency
security updates (#168). The Disclaimer's new player-source paragraph
makes the apps show the consent gate once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
IndexedDB held the catalogue as ~5,568 parsed records (~9.5 MB of
structured-clone objects, readable in DevTools) while fetcher.ts threw
away the pack it had just downloaded. Now the cache stores those packs:
seven Uint8Arrays, ~1.4 MB, opaque. Obfuscation and compression like
the wire packs - the key is public - never protection.
- cache.ts: new database `f2p-catalogue`, the SAME two keys the Privacy
Policy lists (so no policy edit, no consent gate): `f2p:index` (the
DataIndex, readable public metadata) and `f2p:records` (one pack per
index entry). A generation is stored only when every shard arrived
packed - the browser never packs - and every pack's IV must be its
entry's sha256 prefix, or the cache is a miss. Both keys go in one
setMany, records first; the old code's two set() calls could leave a
new index next to old records.
- The copy app <= 2.1.x left in idb-keyval's default `keyval-store` is
read like any verified generation until the next one is written,
which delMany's it. A new database is what keeps a tab still running
old code from reading Uint8Arrays as records; indexedDB.databases() is
checked first so nobody gets an empty legacy database.
- games-loader.ts: readCache() hands back the index at once and the
records lazily, so an older cached generation is never decoded just
to compare it; fetchShard returns { plain, pack } and writeCache gets
the packs. The verify-then-cache contract is unchanged.
- The parser worker opens packs (decodeShard), so a cache hit costs the
main thread ~6 ms at most instead of a ~20 ms block (desktop,
measured), for ~45 ms more until the data is ready.
- Found in the browser: Chromium's failed AES-GCM decrypt is a
DOMException with an EMPTY message, and worker-pool's `if (error)`
read "" as success - a damaged pack resolved as a shard with no
records. The worker now always names the error and the pool rejects
on any string; both have tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 Dependabot alerts (6 high) plus what npm audit adds; npm audit and
pip-audit now report none.
- devalue 5.9.2 -> 5.9.4, brace-expansion 2.1.4 -> 2.1.7 and
5.0.9 -> 5.0.12, fast-uri 3.1.7 -> 3.1.8, serialize-javascript
7.1.1 -> 7.1.2: lockfile only, every parent's range already allowed
the fix. devalue's parser ships in the page and the apps; the rest is
build tooling.
- wrangler 4.130.0 -> 4.147.0: miniflare pins undici exactly, and only
wrangler >= 4.144 brings 7.29.1. Dev and deploy tooling only.
- cookie 0.6.0 -> 0.7.2 under @sveltejs/kit via an override. Kit 2.70.3
is the newest 2.x and still asks for ^0.6.0; it imports only
parse/serialize, which 0.7 keeps, and under adapter-static that code
runs only at prerender and in vite dev. npm refuses a range key for a
direct dependency (EOVERRIDE), hence the exact version; CLAUDE.md says
what to do when kit moves. This also ends the Dependabot security
job that failed on every push to main.
- The sharp 0.35.4 override is dropped: miniflare now pins 0.35.4
itself, and an exact override would force a downgrade the day it
pins a newer one.
- urllib3 2.7.0 -> 2.8.0 for the data pipeline (requests 2.34.2 allows
it).
Verified: npm ci, typecheck, 448 tests, web build + verify-dist, Tauri
flavour build + verify-dist, wrangler deploy --dry-run, vite dev with a
Cookie header, 55 Python tests on urllib3 2.8.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A game's page gets an "All-time peak" row, and the games table a sortable
column ("N/A" sorts to one end, as unrated reviews do); the CSV export
carries the field. The record type mirrors the pipeline's new field.
- The "(peak N)" beside a game's player count is gone. It showed peak_today,
which is the highest of our own occasional samples since the last refetch -
neither a daily peak nor an all-time one - and read like both. Its i18n key
goes with it.
- The Disclaimer's section on player counts names Steam Charts as the source
and says what the number is not: Steam Charts samples periodically, and
for games it does not track the figure is only what this project has seen.
A consent document, so returning visitors see the gate once, showing that
paragraph. The Acknowledgements credit Steam Charts (not a consent
document).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Web app and desktop/Android 2.1.0 -> 2.1.1 (package.json + lock, Cargo.toml
+ the f2p-tracker entry in Cargo.lock, tauri.conf.json, from which the
Android versionCode derives); repo public-facing version 4.1.0 -> 4.1.1.
CHANGELOG's Unreleased section is dated and named, and a fresh empty one
opened above it.
What 2.1.1 brings to the apps: the phone-width layout fixes, the Android
status- and navigation-bar insets, and the Privacy Policy's image-host line
(so the apps show the consent gate once).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The previous commit said documentation AND data commits no longer deploy.
Documentation commits do not; data commits still did: 3f9e8cff ("Refresh store
data [2026-10-02]", four files under data/) carries a Workers Builds check
with a new Version ID, 712b4ab8, at 16:54Z. DEPLOYMENT.md and CLAUDE.md now
state the rule rather than claim it is in force, keep the configuration that
stops both, and say how to verify it: the next bot data commit must have no
Workers Builds check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>