npm (web/):
- undici 7.30.1 through a "miniflare" override (GHSA-xjj6-f33q-929c,
GHSA-4qv8-2p9j-2685, GHSA-f72v-6w45-q472). miniflare pins undici exactly
and wrangler 4.152.0, the newest, still ships 7.29.1. Local tooling only.
- zod 4.6.7 (GHSA-mrhx-c7xc-m3w5, via knip).
- Minor/patch: @lucide/svelte 1.61.0, @tanstack/svelte-virtual 3.13.48,
bits-ui 2.20.2, vite 8.3.5, wrangler 4.152.0, knip 6.43.0,
@tauri-apps/cli 2.12.4.
cargo (web/src-tauri/Cargo.lock, targeted updates only):
- rustls 0.23.46 (RUSTSEC-2026-0346..0349), rustls-webpki 0.103.16
(RUSTSEC-2026-0382), webpki-root-certs 1.0.11 (RUSTSEC-2026-0383),
tokio 1.54.1 (RUSTSEC-2026-0386), anyhow 1.0.104 (RUSTSEC-2026-0190),
event-listener 5.4.2 (RUSTSEC-2026-0221), plist 1.10.3 -> quick-xml
0.42.0 (RUSTSEC-2026-0194/0195). Dependabot had none of these.
- Left upstream: zip 4 (tauri-plugin-updater 2.14.0 asks for ^4), glib 0.18
(GTK 3), unmaintained proc-macro-error/zbus_names/zvariant.
pip: certifi 2026.10.23, coverage 7.17.0 (tests), with every file's hash.
CI: actions/checkout v4/v5 -> v6 and actions/setup-python v5 -> v6
everywhere (the Node 20 majors warned on every data job), rust-cache 2.9.3
by SHA. dependabot.yml says why those majors are taken by hand.
CLAUDE.md: the undici override and when to drop it; why SvelteKit stays on 2
(GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r need setHeaders or use:enhance,
which the app does not have).
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>
- Sixteen setup-python steps move from '3.12' to '3.15'. codeql.yml alone
stays on '3.14': CodeQL's supported-languages page lists Python up to 3.14
and its extractor runs on that interpreter; the pipeline uses no 3.15-only
syntax.
- The updater-json job of release-desktop.yml sets up 3.15 instead of
running the runner image's python3.
- Four text-mode writes name encoding="utf-8": the dead-link log, both
leaderboards and clear_temp(). 3.15 makes UTF-8 the default (PEP 686); on
Windows an older Python writes cp1252, which cannot encode the
leaderboards' emoji, so those scripts crashed there. CI already wrote
UTF-8, so no committed output changes.
- requirements.txt's compile line and sonar.python.version say 3.15.
`uv pip compile --universal` gives the same lock for 3.12 and 3.15, and
every pin installs on 3.15 with --require-hashes --only-binary :all:
(charset-normalizer's cp315 wheels were already hashed).
Checked on Python 3.15.1: the 299 tests pass with EncodingWarning and
DeprecationWarning as errors; edit_game.py --check and delete_game.py
--check pass; a full save_main(load_main()) on a copy of the data leaves all
36 files byte-identical to HEAD, as on 3.14, so no shard and no index.json
changes when the data jobs move.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's GitHub Actions and shell findings, all supply-chain hardening
for jobs that hold a write token (and, in the release workflows, the
signing keys):
- The six third-party actions in release-desktop.yml and release-android.yml
are pinned to the commit their major tag points at today, with the version
in a comment for Dependabot. dtolnay/rust-toolchain is pinned to a master
commit and given `toolchain: stable`: its `stable` branch is regenerated
on top of master, so a commit of it can vanish.
- Every `npm ci` is `npm ci --ignore-scripts`. Only fsevents, workerd and
wrangler's esbuild have install scripts; the last two find their binary in
their optional platform package without them, and fsevents is only file
watching. `npx` is gone from the workflows (`npm run cf:check`,
`npm test -- <file>`).
- requirements.txt pins every runtime package, transitive ones included
(certifi, charset-normalizer, idna), with the sha256 of every file on
PyPI; every install is `--require-hashes --only-binary :all:`. The new
requirements-test.txt holds pytest the same way. python-tests.yml runs the
data jobs' exact install line first, so a Dependabot bump is proven before
a data job meets it.
- `[[ ]]` instead of `[ ]` in the bash wrappers.
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>
isChunkLoadError only matched the three "failed to fetch dynamically imported
module" style messages. Those cover a 404 on a stale chunk, but not what a
host with an SPA fallback returns: a request for a deleted hashed chunk is
answered with index.html at HTTP 200 and Content-Type: text/html, so the
browser rejects it on MIME type instead. The message looks nothing like a
fetch failure, so the reload-once recovery would silently stop working the
moment the site moves behind Cloudflare's not_found_handling. Added the
"failed to load module script" / "expected a javascript module script"
patterns and lifted the regex to a named constant.
Python installs now go through requirements.txt at all 11 sites — nine
bash/*.sh scripts and the two inline workflow steps — instead of a bare
`pip install requests`. The bare install silently ignored the urllib3 pin,
so CI was resolving a dependency the requirements file was trying to
constrain. mark-dead-games.yml already did this correctly.
requirements.txt and requirements-dev.txt move from `>=x,<y` ranges to exact
`==` pins: the pipeline should install identical versions on every run, and
Dependabot does not raise PRs for range-specified dependencies, so the new
pip ecosystem entry in dependabot.yml would otherwise have had nothing to do.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tauri auto-updater
• New tauri-plugin-updater (Rust, target-gated to desktop-only since
iOS/Android reject it). Plugin registered in lib.rs behind
`cfg(not(target_os = "android"|"ios"))`.
• Generated minisign keypair via `tauri signer generate`. PUBLIC key
baked into tauri.conf.json `plugins.updater.pubkey`. Private key
.gitignore'd; the maintainer must mirror it into the repo secret
`TAURI_SIGNING_PRIVATE_KEY` for CI to sign release artefacts.
• New `UpdateChecker` React component runs on Layout mount, lazy-loads
the updater module so the web bundle pays nothing extra. Detects the
Tauri runtime via `window.__TAURI_INTERNALS__`, calls `check()` on
boot, surfaces a sonner toast with Download / Later actions if a
newer signed release is available, streams the .tar.gz / .zip /
.AppImage with progress %, then offers Restart-now via
plugin-process.relaunch().
• Updater endpoint points at the standard
`…/releases/latest/download/latest.json` so each `desktop-v*` tag
automatically becomes the latest available update for installed
clients. tauri-action's `includeUpdaterJson: true` produces this
manifest.
• release-desktop.yml now passes `TAURI_SIGNING_PRIVATE_KEY` +
`_PASSWORD` env vars from secrets so the matrix job signs all
artefacts at build time. Empty secret = builds still work but
updater clients reject unsigned binaries (clear failure mode).
OAuth Device Flow scaffold
Sibling to the PAT panel under Settings — only renders the actual
flow when a CLIENT_ID is configured at build time
(`VITE_GH_OAUTH_CLIENT_ID`). When unconfigured the card explains the
one-time OAuth-app registration steps + the CORS proxy nuance for
browser callers. With CLIENT_ID set, clicking Authorize generates a
one-time `user_code`, opens the GitHub verification page, and polls
/login/oauth/access_token until the user approves — same UX as the
GitHub CLI's `gh auth login --web`. Tauri builds bypass the proxy
requirement because their fetch isn't subject to browser CORS.
Lib + UI:
web/src/lib/oauth-device.ts — requestDeviceCode / pollAccessToken
web/src/components/auth/DeviceFlowPanel.tsx — Settings card
web/src/vite-env.d.ts — typed import.meta.env shim
We deliberately do NOT ship a default CLIENT_ID — sharing the GitHub
CLI's would violate ToS and stamping a public client_id in source
with no app behind it would just dead-end the flow.
CVE / Dependabot bumps (3 moderates → 0)
• web: vite ^5.4.8 → ^7.1.6, vite-plugin-pwa 0.20.5 → 1.0.3,
workbox-window 7.1 → 7.3. Resolves
- GHSA-67mh-4wv8-2f99 Vite path-traversal in optimised .map
- GHSA-67mh-4wv8-2f99 (transitive via vite-plugin-pwa)
- esbuild dev-server SSRF (transitive)
• Python: requests / urllib3 pinned to >= safe versions instead of
fixed ~= ranges so pip picks up future security patches.
• npm audit now reports 0 vulnerabilities; build still 3.79 s under
Vite 7 with no source changes required.
i18n expansion
EditGameDrawer (sign-in dialog, title, subtitles, cancel/back/save
buttons, branch-advanced + save-failed toasts) and Games-page filter
bar (All-genres / All-types / All-platforms / All-status, online /
offline / active / delisted, Clear) now read from the i18n bundles.
Long-form legal copy in /about and docs/* still in English by design.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>